From e45fae43ac8495cd1f8f51d52e87822a2a591279 Mon Sep 17 00:00:00 2001 From: Markus Kruse Date: Fri, 24 Jul 2026 15:02:44 +0200 Subject: [PATCH] =?UTF-8?q?chore:=20Projektinitialisierung=20=E2=80=94=20C?= =?UTF-8?q?-Stone=20Invoice=20Check=20(SaaS-App)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .claude/knowledge-base.md | 55 ++++ .claude/memory.md | 25 ++ .env.example | 32 ++ .gitignore | 15 + .nextcloudignore | 12 + README.md | 48 +++ Task Board.md | 48 +++ backend/__init__.py | 1 + backend/auth.py | 96 ++++++ backend/database.py | 40 +++ backend/main.py | 61 ++++ backend/models.py | 103 ++++++ backend/requirements.txt | 26 ++ backend/routers/__init__.py | 1 + backend/routers/emails.py | 268 +++++++++++++++ backend/routers/invoices.py | 310 ++++++++++++++++++ backend/schemas.py | 0 .../.claude/agent-memory/ledger/MEMORY.md | 10 + .../.claude/agent-memory/scout/MEMORY.md | 7 + .../.claude/agent-memory/sentinel/MEMORY.md | 13 + .../.claude/.claude/agents/compass.md | 78 +++++ .../.claude/.claude/agents/decoder.md | 114 +++++++ .../.claude/.claude/agents/historian.md | 120 +++++++ .../.claude/.claude/agents/ledger.md | 136 ++++++++ .../.claude/.claude/agents/mirror.md | 87 +++++ .../.claude/.claude/agents/pathfinder.md | 100 ++++++ .../.claude/.claude/agents/scout.md | 130 ++++++++ .../.claude/.claude/agents/scribe.md | 112 +++++++ .../.claude/.claude/agents/sentinel.md | 235 +++++++++++++ .../.claude/.claude/command-index.md | 77 +++++ .../.claude/.claude/commands/audit.md | 68 ++++ .../.claude/.claude/commands/brief.md | 148 +++++++++ .../.claude/.claude/commands/check-drift.md | 98 ++++++ .../.claude/commands/create-playbook.md | 87 +++++ .../.claude/.claude/commands/end-day.md | 84 +++++ .../.claude/.claude/commands/flush.md | 90 +++++ .../.claude/.claude/commands/handoff.md | 105 ++++++ .../.claude/.claude/commands/launch.md | 130 ++++++++ .../.claude/.claude/commands/market-scan.md | 133 ++++++++ .../.claude/.claude/commands/onboard.md | 125 +++++++ .../.claude/.claude/commands/proposal.md | 131 ++++++++ .../.claude/.claude/commands/release.md | 107 ++++++ .../.claude/.claude/commands/report.md | 112 +++++++ .../.claude/.claude/commands/retro.md | 85 +++++ .../.claude/.claude/commands/review.md | 100 ++++++ .../.claude/.claude/commands/standup.md | 74 +++++ .../.claude/.claude/commands/start.md | 73 +++++ .../.claude/.claude/commands/sync.md | 77 +++++ .../.claude/.claude/commands/system-audit.md | 92 ++++++ .../.claude/.claude/commands/tech-debt.md | 116 +++++++ .../.claude/.claude/commands/unstick.md | 64 ++++ .../.claude/hooks/backup-before-write.sh | 29 ++ .../.claude/hooks/completeness-gate.sh | 190 +++++++++++ .../.claude/.claude/hooks/guard-bash.sh | 154 +++++++++ .../.claude/.claude/hooks/log-changes.sh | 22 ++ .../.claude/.claude/hooks/log-failures.sh | 57 ++++ .../.claude/.claude/hooks/log-stop-verdict.sh | 71 ++++ .../.claude/hooks/post-compact-resume.sh | 26 ++ .../.claude/hooks/pre-compact-handoff.sh | 14 + .../.claude/.claude/hooks/session-reset.sh | 79 +++++ .../.claude/.claude/knowledge-base.md | 23 ++ .../.claude/.claude/knowledge-nominations.md | 6 + clowdex-download/.claude/.claude/memory.md | 13 + .../.claude/.claude/settings.json | 115 +++++++ .../.claude/.claude/skills/INDEX.md | 68 ++++ .../agriculture/animal-welfare-audit/SKILL.md | 131 ++++++++ .../skills/agriculture/breeding-plan/SKILL.md | 131 ++++++++ .../agriculture/carbon-footprint/SKILL.md | 131 ++++++++ .../agriculture/conservation-plan/SKILL.md | 131 ++++++++ .../skills/agriculture/cost-per-acre/SKILL.md | 131 ++++++++ .../skills/agriculture/crop-plan/SKILL.md | 131 ++++++++ .../skills/agriculture/csa-program/SKILL.md | 131 ++++++++ .../agriculture/direct-to-consumer/SKILL.md | 131 ++++++++ .../disaster-preparedness-farm/SKILL.md | 131 ++++++++ .../equipment-maintenance-farm/SKILL.md | 131 ++++++++ .../skills/agriculture/equipment-roi/SKILL.md | 131 ++++++++ .../skills/agriculture/farm-budget/SKILL.md | 131 ++++++++ .../agriculture/farm-business-plan/SKILL.md | 131 ++++++++ .../agriculture/farm-marketing/SKILL.md | 131 ++++++++ .../agriculture/farmers-market-plan/SKILL.md | 131 ++++++++ .../agriculture/feed-management/SKILL.md | 131 ++++++++ .../agriculture/fertilizer-plan/SKILL.md | 131 ++++++++ .../grant-application-agriculture/SKILL.md | 131 ++++++++ .../skills/agriculture/harvest-plan/SKILL.md | 131 ++++++++ .../health-protocol-livestock/SKILL.md | 131 ++++++++ .../insurance-review-farm/SKILL.md | 131 ++++++++ .../integrated-pest-management/SKILL.md | 131 ++++++++ .../agriculture/irrigation-schedule/SKILL.md | 131 ++++++++ .../labor-management-farm/SKILL.md | 131 ++++++++ .../agriculture/land-acquisition/SKILL.md | 131 ++++++++ .../lease-negotiation-farm/SKILL.md | 131 ++++++++ .../agriculture/livestock-management/SKILL.md | 131 ++++++++ .../organic-certification/SKILL.md | 131 ++++++++ .../agriculture/pasture-rotation/SKILL.md | 131 ++++++++ .../agriculture/pest-management/SKILL.md | 131 ++++++++ .../agriculture/planting-schedule/SKILL.md | 131 ++++++++ .../post-harvest-handling/SKILL.md | 131 ++++++++ .../agriculture/profit-analysis-farm/SKILL.md | 131 ++++++++ .../regenerative-practices/SKILL.md | 131 ++++++++ .../agriculture/seasonal-hiring/SKILL.md | 131 ++++++++ .../agriculture/soil-analysis-plan/SKILL.md | 131 ++++++++ .../skills/agriculture/storage-plan/SKILL.md | 131 ++++++++ .../agriculture/subsidy-tracker/SKILL.md | 131 ++++++++ .../succession-planning-farm/SKILL.md | 131 ++++++++ .../sustainability-report-farm/SKILL.md | 131 ++++++++ .../agriculture/technology-adoption/SKILL.md | 131 ++++++++ .../agriculture/value-added-product/SKILL.md | 131 ++++++++ .../agriculture/weather-contingency/SKILL.md | 131 ++++++++ .../agriculture/wholesale-channel/SKILL.md | 131 ++++++++ .../agriculture/worker-safety-farm/SKILL.md | 131 ++++++++ .../ai-automation/agent-evaluation/SKILL.md | 132 ++++++++ .../ai-automation/ai-adoption-plan/SKILL.md | 132 ++++++++ .../ai-automation/ai-agent-design/SKILL.md | 132 ++++++++ .../ai-automation/ai-assistant-spec/SKILL.md | 132 ++++++++ .../ai-automation/ai-bias-audit/SKILL.md | 131 ++++++++ .../ai-change-management/SKILL.md | 132 ++++++++ .../ai-automation/ai-code-review/SKILL.md | 132 ++++++++ .../ai-compliance-documentation/SKILL.md | 131 ++++++++ .../ai-content-pipeline/SKILL.md | 132 ++++++++ .../ai-content-policy-framework/SKILL.md | 131 ++++++++ .../ai-cost-optimization/SKILL.md | 131 ++++++++ .../ai-customer-service/SKILL.md | 132 ++++++++ .../ai-automation/ai-data-analysis/SKILL.md | 132 ++++++++ .../ai-debugging-workflow/SKILL.md | 132 ++++++++ .../ai-editing-workflow/SKILL.md | 132 ++++++++ .../ai-automation/ai-email-drafting/SKILL.md | 132 ++++++++ .../ai-ethics-checklist/SKILL.md | 132 ++++++++ .../ai-financial-compliance/SKILL.md | 131 ++++++++ .../ai-healthcare-compliance/SKILL.md | 131 ++++++++ .../ai-automation/ai-image-prompt/SKILL.md | 132 ++++++++ .../ai-automation/ai-image-workflow/SKILL.md | 132 ++++++++ .../ai-automation/ai-meeting-notes/SKILL.md | 132 ++++++++ .../ai-pair-programming/SKILL.md | 132 ++++++++ .../ai-readiness-assessment/SKILL.md | 132 ++++++++ .../ai-research-workflow/SKILL.md | 132 ++++++++ .../skills/ai-automation/ai-strategy/SKILL.md | 132 ++++++++ .../ai-automation/ai-summarization/SKILL.md | 132 ++++++++ .../ai-training-program/SKILL.md | 132 ++++++++ .../ai-transcription-workflow/SKILL.md | 132 ++++++++ .../ai-translation-workflow/SKILL.md | 132 ++++++++ .../ai-use-case-identification/SKILL.md | 132 ++++++++ .../ai-ux-design-patterns/SKILL.md | 131 ++++++++ .../ai-vendor-evaluation/SKILL.md | 131 ++++++++ .../ai-automation/ai-voice-workflow/SKILL.md | 132 ++++++++ .../ai-automation/ai-workflow-design/SKILL.md | 132 ++++++++ .../ai-writing-workflow/SKILL.md | 132 ++++++++ .../algorithmic-impact-assessment/SKILL.md | 131 ++++++++ .../api-integration-plan/SKILL.md | 132 ++++++++ .../automation-opportunity-map/SKILL.md | 132 ++++++++ .../automation-roi-calculator/SKILL.md | 132 ++++++++ .../ai-automation/chatbot-design/SKILL.md | 132 ++++++++ .../conversational-flow/SKILL.md | 132 ++++++++ .../ai-automation/creative-ai-brief/SKILL.md | 132 ++++++++ .../enterprise-ai-governance/SKILL.md | 131 ++++++++ .../eu-ai-act-compliance/SKILL.md | 131 ++++++++ .../ai-automation/fine-tuning-plan/SKILL.md | 132 ++++++++ .../intelligent-automation/SKILL.md | 132 ++++++++ .../ai-automation/knowledge-base-ai/SKILL.md | 132 ++++++++ .../llm-application-architecture/SKILL.md | 131 ++++++++ .../ai-automation/llm-comparison/SKILL.md | 132 ++++++++ .../ai-automation/make-workflow/SKILL.md | 132 ++++++++ .../multi-agent-workflow/SKILL.md | 132 ++++++++ .../ai-automation/n8n-workflow/SKILL.md | 132 ++++++++ .../ai-automation/no-code-automation/SKILL.md | 132 ++++++++ .../ai-automation/process-mining/SKILL.md | 132 ++++++++ .../prompt-engineering-guide/SKILL.md | 132 ++++++++ .../prompt-evaluation-harness/SKILL.md | 131 ++++++++ .../prompt-template-builder/SKILL.md | 132 ++++++++ .../prompt-testing-plan/SKILL.md | 132 ++++++++ .../ai-automation/rag-system-design/SKILL.md | 132 ++++++++ .../responsible-ai-framework/SKILL.md | 132 ++++++++ .../ai-automation/rpa-assessment/SKILL.md | 132 ++++++++ .../synthetic-data-strategy/SKILL.md | 131 ++++++++ .../ai-automation/webhook-design/SKILL.md | 132 ++++++++ .../ai-automation/zapier-workflow/SKILL.md | 132 ++++++++ .../apprenticeship-program/SKILL.md | 131 ++++++++ .../as-built-documentation/SKILL.md | 131 ++++++++ .../construction/bid-submission/SKILL.md | 131 ++++++++ .../budget-tracking-construction/SKILL.md | 131 ++++++++ .../skills/construction/change-order/SKILL.md | 131 ++++++++ .../client-update-construction/SKILL.md | 131 ++++++++ .../construction/code-compliance/SKILL.md | 131 ++++++++ .../completion-certificate/SKILL.md | 131 ++++++++ .../cost-variance-analysis/SKILL.md | 131 ++++++++ .../construction/critical-path/SKILL.md | 131 ++++++++ .../employee-certification-tracker/SKILL.md | 131 ++++++++ .../environmental-assessment/SKILL.md | 131 ++++++++ .../equipment-maintenance/SKILL.md | 131 ++++++++ .../construction/fleet-management/SKILL.md | 131 ++++++++ .../gantt-chart-construction/SKILL.md | 131 ++++++++ .../construction/incident-report/SKILL.md | 131 ++++++++ .../inspection-checklist/SKILL.md | 131 ++++++++ .../construction/labor-estimate/SKILL.md | 131 ++++++++ .../construction/maintenance-manual/SKILL.md | 131 ++++++++ .../marketing-construction/SKILL.md | 131 ++++++++ .../construction/material-takeoff/SKILL.md | 131 ++++++++ .../construction/payment-application/SKILL.md | 131 ++++++++ .../construction/permit-checklist/SKILL.md | 131 ++++++++ .../construction/portfolio-showcase/SKILL.md | 131 ++++++++ .../progress-report-construction/SKILL.md | 131 ++++++++ .../construction/project-estimate/SKILL.md | 131 ++++++++ .../project-proposal-construction/SKILL.md | 131 ++++++++ .../construction/project-schedule/SKILL.md | 131 ++++++++ .../skills/construction/punch-list/SKILL.md | 131 ++++++++ .../quality-control-construction/SKILL.md | 131 ++++++++ .../referral-strategy-construction/SKILL.md | 131 ++++++++ .../skills/construction/safety-plan/SKILL.md | 131 ++++++++ .../construction/safety-training/SKILL.md | 131 ++++++++ .../scope-of-work-construction/SKILL.md | 131 ++++++++ .../construction/site-assessment/SKILL.md | 131 ++++++++ .../construction/soil-report-summary/SKILL.md | 131 ++++++++ .../subcontractor-agreement/SKILL.md | 131 ++++++++ .../subcontractor-evaluation/SKILL.md | 131 ++++++++ .../construction/tool-inventory/SKILL.md | 131 ++++++++ .../skills/construction/toolbox-talk/SKILL.md | 131 ++++++++ .../construction/warranty-document/SKILL.md | 131 ++++++++ .../construction/zoning-analysis/SKILL.md | 131 ++++++++ .../skills/consulting/100-day-plan/SKILL.md | 132 ++++++++ .../consulting/benchmarking-study/SKILL.md | 132 ++++++++ .../consulting/board-presentation/SKILL.md | 132 ++++++++ .../skills/consulting/build-vs-buy/SKILL.md | 132 ++++++++ .../consulting/capability-building/SKILL.md | 132 ++++++++ .../consulting/change-readiness/SKILL.md | 132 ++++++++ .../client-discovery-workshop/SKILL.md | 132 ++++++++ .../consulting/client-proposal/SKILL.md | 132 ++++++++ .../core-competency-analysis/SKILL.md | 132 ++++++++ .../consulting/cost-optimization/SKILL.md | 132 ++++++++ .../consulting/culture-assessment/SKILL.md | 132 ++++++++ .../current-state-assessment/SKILL.md | 132 ++++++++ .../customer-experience-audit/SKILL.md | 132 ++++++++ .../digital-transformation-plan/SKILL.md | 132 ++++++++ .../consulting/disruption-analysis/SKILL.md | 132 ++++++++ .../diversification-analysis/SKILL.md | 132 ++++++++ .../due-diligence-commercial/SKILL.md | 132 ++++++++ .../consulting/engagement-letter/SKILL.md | 132 ++++++++ .../executive-presentation/SKILL.md | 132 ++++++++ .../consulting/expansion-strategy/SKILL.md | 132 ++++++++ .../skills/consulting/gap-analysis/SKILL.md | 132 ++++++++ .../implementation-roadmap/SKILL.md | 132 ++++++++ .../consulting/industry-analysis/SKILL.md | 132 ++++++++ .../consulting/innovation-strategy/SKILL.md | 132 ++++++++ .../consulting/integration-planning/SKILL.md | 132 ++++++++ .../consulting/journey-mapping/SKILL.md | 132 ++++++++ .../consulting/knowledge-management/SKILL.md | 132 ++++++++ .../consulting/lean-assessment/SKILL.md | 132 ++++++++ .../consulting/market-entry-strategy/SKILL.md | 132 ++++++++ .../consulting/market-landscape/SKILL.md | 132 ++++++++ .../skills/consulting/maturity-model/SKILL.md | 132 ++++++++ .../consulting/operating-model/SKILL.md | 132 ++++++++ .../organizational-assessment/SKILL.md | 132 ++++++++ .../consulting/pestel-analysis/SKILL.md | 132 ++++++++ .../consulting/porters-five-forces/SKILL.md | 132 ++++++++ .../post-merger-integration/SKILL.md | 132 ++++++++ .../consulting/process-improvement/SKILL.md | 132 ++++++++ .../consulting/recommendation-deck/SKILL.md | 132 ++++++++ .../consulting/red-team-exercise/SKILL.md | 132 ++++++++ .../scenario-planning-consulting/SKILL.md | 132 ++++++++ .../skills/consulting/scope-of-work/SKILL.md | 132 ++++++++ .../skills/consulting/service-design/SKILL.md | 132 ++++++++ .../consulting/shared-services/SKILL.md | 132 ++++++++ .../consulting/six-sigma-project/SKILL.md | 132 ++++++++ .../stakeholder-interview-guide/SKILL.md | 132 ++++++++ .../consulting/strategy-framework/SKILL.md | 132 ++++++++ .../skills/consulting/swot-analysis/SKILL.md | 132 ++++++++ .../consulting/talent-strategy/SKILL.md | 132 ++++++++ .../consulting/technology-assessment/SKILL.md | 132 ++++++++ .../transformation-roadmap/SKILL.md | 132 ++++++++ .../trend-analysis-consulting/SKILL.md | 132 ++++++++ .../consulting/value-chain-analysis/SKILL.md | 132 ++++++++ .../consulting/vendor-selection/SKILL.md | 132 ++++++++ .../skills/consulting/war-gaming/SKILL.md | 132 ++++++++ .../skills/content/about-page-copy/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-facebook/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-google/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-linkedin/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-tiktok/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-twitter/SKILL.md | 133 ++++++++ .../skills/content/ad-copy-youtube/SKILL.md | 133 ++++++++ .../content/annual-report-narrative/SKILL.md | 133 ++++++++ .../skills/content/api-documentation/SKILL.md | 133 ++++++++ .../content/blog-content-calendar/SKILL.md | 133 ++++++++ .../.claude/skills/content/blog-post/SKILL.md | 133 ++++++++ .../skills/content/blog-series-plan/SKILL.md | 133 ++++++++ .../skills/content/brand-story/SKILL.md | 133 ++++++++ .../content/business-proposal-copy/SKILL.md | 133 ++++++++ .../skills/content/byline-article/SKILL.md | 133 ++++++++ .../skills/content/case-study/SKILL.md | 133 ++++++++ .../.claude/skills/content/changelog/SKILL.md | 133 ++++++++ .../skills/content/checkout-copy/SKILL.md | 133 ++++++++ .../skills/content/company-update/SKILL.md | 133 ++++++++ .../content/comparison-article/SKILL.md | 133 ++++++++ .../content/content-atomization/SKILL.md | 133 ++++++++ .../skills/content/content-audit/SKILL.md | 133 ++++++++ .../skills/content/content-brief/SKILL.md | 133 ++++++++ .../content/content-gap-analysis/SKILL.md | 133 ++++++++ .../content/content-repurposing/SKILL.md | 133 ++++++++ .../skills/content/cta-optimizer/SKILL.md | 133 ++++++++ .../skills/content/customer-story/SKILL.md | 133 ++++++++ .../skills/content/documentation/SKILL.md | 133 ++++++++ .../skills/content/ebook-chapter/SKILL.md | 133 ++++++++ .../skills/content/ebook-outline/SKILL.md | 133 ++++++++ .../content/elevator-pitch-copy/SKILL.md | 133 ++++++++ .../skills/content/email-body-copy/SKILL.md | 133 ++++++++ .../content/email-sequence-copy/SKILL.md | 133 ++++++++ .../content/email-subject-lines/SKILL.md | 133 ++++++++ .../skills/content/empty-state-copy/SKILL.md | 133 ++++++++ .../content/error-message-copy/SKILL.md | 133 ++++++++ .../content/explainer-video-script/SKILL.md | 133 ++++++++ .../.claude/skills/content/faq-page/SKILL.md | 133 ++++++++ .../content/feature-comparison/SKILL.md | 133 ++++++++ .../skills/content/grant-proposal/SKILL.md | 133 ++++++++ .../content/headline-generator/SKILL.md | 133 ++++++++ .../skills/content/homepage-copy/SKILL.md | 133 ++++++++ .../skills/content/how-to-guide/SKILL.md | 133 ++++++++ .../content/in-app-message-copy/SKILL.md | 133 ++++++++ .../skills/content/industry-report/SKILL.md | 133 ++++++++ .../skills/content/investor-update/SKILL.md | 133 ++++++++ .../skills/content/keynote-outline/SKILL.md | 133 ++++++++ .../skills/content/landing-page-copy/SKILL.md | 133 ++++++++ .../.claude/skills/content/listicle/SKILL.md | 133 ++++++++ .../skills/content/manifesto-writer/SKILL.md | 133 ++++++++ .../skills/content/media-advisory/SKILL.md | 133 ++++++++ .../skills/content/microcopy-audit/SKILL.md | 133 ++++++++ .../skills/content/mission-statement/SKILL.md | 133 ++++++++ .../skills/content/naming-brainstorm/SKILL.md | 133 ++++++++ .../skills/content/newsletter-issue/SKILL.md | 133 ++++++++ .../content/newsletter-strategy/SKILL.md | 133 ++++++++ .../newsletter-welcome-series/SKILL.md | 133 ++++++++ .../skills/content/onboarding-copy/SKILL.md | 133 ++++++++ .../skills/content/opinion-piece/SKILL.md | 133 ++++++++ .../skills/content/origin-story/SKILL.md | 133 ++++++++ .../skills/content/pillar-page/SKILL.md | 133 ++++++++ .../content/podcast-episode-plan/SKILL.md | 133 ++++++++ .../skills/content/podcast-outline/SKILL.md | 133 ++++++++ .../content/podcast-show-notes/SKILL.md | 133 ++++++++ .../content/presentation-script/SKILL.md | 133 ++++++++ .../content/press-release-writer/SKILL.md | 133 ++++++++ .../skills/content/pricing-page-copy/SKILL.md | 133 ++++++++ .../content/product-description/SKILL.md | 133 ++++++++ .../skills/content/product-page-copy/SKILL.md | 133 ++++++++ .../content/push-notification-copy/SKILL.md | 133 ++++++++ .../skills/content/release-notes/SKILL.md | 133 ++++++++ .../skills/content/rfp-response/SKILL.md | 133 ++++++++ .../skills/content/slogan-generator/SKILL.md | 133 ++++++++ .../.claude/skills/content/sms-copy/SKILL.md | 133 ++++++++ .../skills/content/social-proof-page/SKILL.md | 133 ++++++++ .../skills/content/speech-writer/SKILL.md | 133 ++++++++ .../skills/content/style-guide/SKILL.md | 133 ++++++++ .../content/tagline-brainstorm/SKILL.md | 133 ++++++++ .../skills/content/technical-writing/SKILL.md | 133 ++++++++ .../content/testimonial-request/SKILL.md | 133 ++++++++ .../thought-leadership-article/SKILL.md | 133 ++++++++ .../content/tone-of-voice-guide/SKILL.md | 133 ++++++++ .../skills/content/tutorial-script/SKILL.md | 133 ++++++++ .../skills/content/user-guide/SKILL.md | 133 ++++++++ .../content/value-proposition-copy/SKILL.md | 133 ++++++++ .../skills/content/video-script/SKILL.md | 133 ++++++++ .../skills/content/vision-statement/SKILL.md | 133 ++++++++ .../skills/content/whitepaper/SKILL.md | 133 ++++++++ .../advocacy-program/SKILL.md | 132 ++++++++ .../ai-support-setup/SKILL.md | 132 ++++++++ .../beta-tester-program/SKILL.md | 132 ++++++++ .../certification-program/SKILL.md | 132 ++++++++ .../champion-program/SKILL.md | 132 ++++++++ .../chatbot-conversation-design/SKILL.md | 132 ++++++++ .../chatbot-decision-tree/SKILL.md | 132 ++++++++ .../churn-prevention-playbook/SKILL.md | 132 ++++++++ .../churn-risk-analysis/SKILL.md | 132 ++++++++ .../community-management/SKILL.md | 132 ++++++++ .../customer-success/cs-cadence-plan/SKILL.md | 132 ++++++++ .../customer-success/csat-survey/SKILL.md | 132 ++++++++ .../customer-advisory-board/SKILL.md | 132 ++++++++ .../customer-communication-plan/SKILL.md | 132 ++++++++ .../customer-effort-score/SKILL.md | 132 ++++++++ .../customer-feedback-loop/SKILL.md | 132 ++++++++ .../customer-health-score/SKILL.md | 132 ++++++++ .../customer-journey-optimization/SKILL.md | 132 ++++++++ .../customer-onboarding-plan/SKILL.md | 132 ++++++++ .../customer-success-playbook/SKILL.md | 132 ++++++++ .../customer-training-plan/SKILL.md | 132 ++++++++ .../customer-welcome-kit/SKILL.md | 132 ++++++++ .../escalation-procedure/SKILL.md | 132 ++++++++ .../expansion-playbook/SKILL.md | 132 ++++++++ .../experience-mapping/SKILL.md | 132 ++++++++ .../feature-announcement/SKILL.md | 132 ++++++++ .../feedback-categorization/SKILL.md | 132 ++++++++ .../forum-moderation-guide/SKILL.md | 132 ++++++++ .../friction-point-analysis/SKILL.md | 132 ++++++++ .../help-center-structure/SKILL.md | 132 ++++++++ .../implementation-plan/SKILL.md | 132 ++++++++ .../knowledge-base-article-support/SKILL.md | 132 ++++++++ .../nps-survey-design/SKILL.md | 132 ++++++++ .../outage-communication/SKILL.md | 132 ++++++++ .../customer-success/qbr-template/SKILL.md | 132 ++++++++ .../quality-assurance-support/SKILL.md | 132 ++++++++ .../renewal-playbook/SKILL.md | 132 ++++++++ .../response-time-analysis/SKILL.md | 132 ++++++++ .../self-service-strategy/SKILL.md | 132 ++++++++ .../customer-success/sla-definition/SKILL.md | 132 ++++++++ .../support-metrics-dashboard/SKILL.md | 132 ++++++++ .../support-retrospective/SKILL.md | 132 ++++++++ .../support-team-training/SKILL.md | 132 ++++++++ .../support-ticket-template/SKILL.md | 132 ++++++++ .../tier-support-guide/SKILL.md | 132 ++++++++ .../customer-success/user-group-plan/SKILL.md | 132 ++++++++ .../voice-of-customer/SKILL.md | 132 ++++++++ .../customer-success/webinar-series/SKILL.md | 132 ++++++++ .../access-control-matrix/SKILL.md | 131 ++++++++ .../api-security-assessment/SKILL.md | 131 ++++++++ .../attack-surface-analysis/SKILL.md | 133 ++++++++ .../backup-validation-report/SKILL.md | 131 ++++++++ .../.claude/skills/cybersecurity/bcp/SKILL.md | 131 ++++++++ .../board-security-report/SKILL.md | 131 ++++++++ .../cloud-security-assessment/SKILL.md | 133 ++++++++ .../compliance-gap-analysis/SKILL.md | 131 ++++++++ .../data-breach-notification/SKILL.md | 131 ++++++++ .../data-classification-policy/SKILL.md | 131 ++++++++ .../cybersecurity/detection-rule/SKILL.md | 131 ++++++++ .../disaster-recovery-plan/SKILL.md | 131 ++++++++ .../skills/cybersecurity/dpia/SKILL.md | 131 ++++++++ .../encryption-standard/SKILL.md | 131 ++++++++ .../cybersecurity/forensics-report/SKILL.md | 131 ++++++++ .../cybersecurity/hipaa-assessment/SKILL.md | 131 ++++++++ .../skills/cybersecurity/iam-review/SKILL.md | 131 ++++++++ .../cybersecurity/incident-report/SKILL.md | 131 ++++++++ .../incident-response-plan/SKILL.md | 131 ++++++++ .../skills/cybersecurity/ir-playbook/SKILL.md | 131 ++++++++ .../cybersecurity/iso27001-isms/SKILL.md | 131 ++++++++ .../network-security-design/SKILL.md | 131 ++++++++ .../nist-csf-assessment/SKILL.md | 131 ++++++++ .../skills/cybersecurity/pam-policy/SKILL.md | 131 ++++++++ .../cybersecurity/pci-dss-assessment/SKILL.md | 131 ++++++++ .../cybersecurity/pentest-report/SKILL.md | 134 ++++++++ .../phishing-simulation-report/SKILL.md | 131 ++++++++ .../privacy-program-plan/SKILL.md | 131 ++++++++ .../cybersecurity/purple-team-report/SKILL.md | 133 ++++++++ .../cybersecurity/red-team-report/SKILL.md | 133 ++++++++ .../cybersecurity/risk-assessment/SKILL.md | 131 ++++++++ .../cybersecurity/risk-register/SKILL.md | 131 ++++++++ .../skills/cybersecurity/runbook/SKILL.md | 131 ++++++++ .../skills/cybersecurity/sbom/SKILL.md | 131 ++++++++ .../sdlc-security-gates/SKILL.md | 131 ++++++++ .../cybersecurity/secure-code-review/SKILL.md | 131 ++++++++ .../cybersecurity/secure-design-spec/SKILL.md | 131 ++++++++ .../security-architecture-review/SKILL.md | 132 ++++++++ .../security-awareness-program/SKILL.md | 131 ++++++++ .../security-monitoring-plan/SKILL.md | 131 ++++++++ .../cybersecurity/security-policy/SKILL.md | 131 ++++++++ .../soc-maturity-assessment/SKILL.md | 131 ++++++++ .../cybersecurity/soc-playbook/SKILL.md | 131 ++++++++ .../skills/cybersecurity/soc2-report/SKILL.md | 131 ++++++++ .../social-engineering-assessment/SKILL.md | 133 ++++++++ .../cybersecurity/tabletop-exercise/SKILL.md | 131 ++++++++ .../threat-intel-report/SKILL.md | 133 ++++++++ .../threat-landscape-briefing/SKILL.md | 133 ++++++++ .../cybersecurity/threat-model/SKILL.md | 133 ++++++++ .../vendor-risk-assessment/SKILL.md | 131 ++++++++ .../cybersecurity/vuln-assessment/SKILL.md | 133 ++++++++ .../cybersecurity/web-app-assessment/SKILL.md | 133 ++++++++ .../wireless-security-assessment/SKILL.md | 133 ++++++++ .../cybersecurity/zero-trust-design/SKILL.md | 132 ++++++++ .../skills/data/ab-test-analysis/SKILL.md | 131 ++++++++ .../analytics-implementation-plan/SKILL.md | 131 ++++++++ .../skills/data/attribution-analysis/SKILL.md | 131 ++++++++ .../skills/data/benchmark-analysis/SKILL.md | 131 ++++++++ .../data/chart-selection-guide/SKILL.md | 131 ++++++++ .../skills/data/clustering-analysis/SKILL.md | 131 ++++++++ .../skills/data/cohort-analysis/SKILL.md | 131 ++++++++ .../data/competitive-data-analysis/SKILL.md | 131 ++++++++ .../data/customer-segmentation/SKILL.md | 131 ++++++++ .../skills/data/dashboard-design/SKILL.md | 131 ++++++++ .../skills/data/data-access-control/SKILL.md | 131 ++++++++ .../skills/data/data-analysis-plan/SKILL.md | 131 ++++++++ .../.claude/skills/data/data-catalog/SKILL.md | 131 ++++++++ .../skills/data/data-cleaning-plan/SKILL.md | 131 ++++++++ .../skills/data/data-dictionary/SKILL.md | 131 ++++++++ .../data/data-driven-recommendation/SKILL.md | 131 ++++++++ .../data/data-governance-policy/SKILL.md | 131 ++++++++ .../skills/data/data-mart-design/SKILL.md | 131 ++++++++ .../skills/data/data-privacy-impact/SKILL.md | 131 ++++++++ .../skills/data/data-quality-audit/SKILL.md | 131 ++++++++ .../skills/data/data-storytelling/SKILL.md | 131 ++++++++ .../skills/data/data-validation/SKILL.md | 131 ++++++++ .../skills/data/data-visualization/SKILL.md | 131 ++++++++ .../data/data-warehouse-schema/SKILL.md | 131 ++++++++ .../skills/data/database-performance/SKILL.md | 131 ++++++++ .../skills/data/etl-pipeline-design/SKILL.md | 131 ++++++++ .../skills/data/event-taxonomy/SKILL.md | 131 ++++++++ .../skills/data/executive-dashboard/SKILL.md | 131 ++++++++ .../skills/data/experiment-results/SKILL.md | 131 ++++++++ .../data/exploratory-data-analysis/SKILL.md | 131 ++++++++ .../skills/data/forecasting-model/SKILL.md | 131 ++++++++ .../skills/data/funnel-analysis/SKILL.md | 131 ++++++++ .../skills/data/incrementality-test/SKILL.md | 131 ++++++++ .../skills/data/industry-data-report/SKILL.md | 131 ++++++++ .../skills/data/infographic-spec/SKILL.md | 131 ++++++++ .../skills/data/insight-presentation/SKILL.md | 131 ++++++++ .../skills/data/kpi-dashboard/SKILL.md | 131 ++++++++ .../skills/data/marketing-mix-model/SKILL.md | 131 ++++++++ .../skills/data/metadata-management/SKILL.md | 131 ++++++++ .../skills/data/ml-experiment-plan/SKILL.md | 131 ++++++++ .../skills/data/model-evaluation/SKILL.md | 131 ++++++++ .../skills/data/monthly-report/SKILL.md | 131 ++++++++ .../.claude/skills/data/nps-analysis/SKILL.md | 131 ++++++++ .../data/predictive-model-spec/SKILL.md | 131 ++++++++ .../skills/data/query-optimization/SKILL.md | 131 ++++++++ .../skills/data/report-template/SKILL.md | 131 ++++++++ .../skills/data/retention-analysis/SKILL.md | 131 ++++++++ .../.claude/skills/data/rfm-analysis/SKILL.md | 131 ++++++++ .../skills/data/sql-query-builder/SKILL.md | 131 ++++++++ .../skills/data/statistical-analysis/SKILL.md | 131 ++++++++ .../data/statistical-significance/SKILL.md | 131 ++++++++ .../skills/data/survey-analysis/SKILL.md | 131 ++++++++ .../skills/data/survey-design/SKILL.md | 131 ++++++++ .../skills/data/time-series-analysis/SKILL.md | 131 ++++++++ .../skills/data/tracking-plan/SKILL.md | 131 ++++++++ .../skills/data/trend-analysis/SKILL.md | 131 ++++++++ .../skills/data/weekly-report/SKILL.md | 131 ++++++++ .../accessibility-design-guide/SKILL.md | 132 ++++++++ .../skills/design/animation-brief/SKILL.md | 132 ++++++++ .../design/art-direction-guide/SKILL.md | 132 ++++++++ .../design/brand-application-guide/SKILL.md | 132 ++++++++ .../design/brand-asset-library/SKILL.md | 132 ++++++++ .../design/brand-guidelines-doc/SKILL.md | 132 ++++++++ .../design/brand-identity-system/SKILL.md | 132 ++++++++ .../design/campaign-creative-brief/SKILL.md | 132 ++++++++ .../design/color-palette-guide/SKILL.md | 132 ++++++++ .../design/component-library-spec/SKILL.md | 132 ++++++++ .../skills/design/creative-brief/SKILL.md | 132 ++++++++ .../design/creative-campaign-concept/SKILL.md | 132 ++++++++ .../design/creative-review-checklist/SKILL.md | 132 ++++++++ .../design/data-visualization-guide/SKILL.md | 132 ++++++++ .../skills/design/design-brief/SKILL.md | 132 ++++++++ .../design/design-critique-guide/SKILL.md | 132 ++++++++ .../skills/design/design-handoff/SKILL.md | 132 ++++++++ .../skills/design/design-sprint/SKILL.md | 132 ++++++++ .../skills/design/design-system/SKILL.md | 132 ++++++++ .../design/design-thinking-workshop/SKILL.md | 132 ++++++++ .../skills/design/design-tokens/SKILL.md | 132 ++++++++ .../skills/design/email-design-brief/SKILL.md | 132 ++++++++ .../skills/design/icon-system/SKILL.md | 132 ++++++++ .../skills/design/ideation-session/SKILL.md | 132 ++++++++ .../design/illustration-style-guide/SKILL.md | 132 ++++++++ .../inclusive-design-checklist/SKILL.md | 132 ++++++++ .../skills/design/infographic-brief/SKILL.md | 132 ++++++++ .../design/information-architecture/SKILL.md | 132 ++++++++ .../design/interaction-design-spec/SKILL.md | 132 ++++++++ .../design/landing-page-design-brief/SKILL.md | 132 ++++++++ .../.claude/skills/design/logo-brief/SKILL.md | 132 ++++++++ .../design/mobile-design-guide/SKILL.md | 132 ++++++++ .../.claude/skills/design/mood-board/SKILL.md | 132 ++++++++ .../design/packaging-design-brief/SKILL.md | 132 ++++++++ .../.claude/skills/design/persona-ux/SKILL.md | 132 ++++++++ .../design/photo-direction-brief/SKILL.md | 132 ++++++++ .../design/presentation-design-guide/SKILL.md | 132 ++++++++ .../skills/design/print-design-brief/SKILL.md | 132 ++++++++ .../skills/design/prototype-spec/SKILL.md | 132 ++++++++ .../design/responsive-design-spec/SKILL.md | 132 ++++++++ .../skills/design/signage-brief/SKILL.md | 132 ++++++++ .../design/social-media-design-brief/SKILL.md | 132 ++++++++ .../.claude/skills/design/storyboard/SKILL.md | 132 ++++++++ .../.claude/skills/design/style-tile/SKILL.md | 132 ++++++++ .../design/tablet-design-guide/SKILL.md | 132 ++++++++ .../skills/design/typography-system/SKILL.md | 132 ++++++++ .../skills/design/usability-test/SKILL.md | 132 ++++++++ .../.claude/skills/design/user-flow/SKILL.md | 132 ++++++++ .../skills/design/user-interview-ux/SKILL.md | 132 ++++++++ .../skills/design/ux-research-plan/SKILL.md | 132 ++++++++ .../design/video-direction-brief/SKILL.md | 132 ++++++++ .../skills/design/visual-direction/SKILL.md | 132 ++++++++ .../.claude/skills/design/wcag-audit/SKILL.md | 132 ++++++++ .../skills/design/wireframe-spec/SKILL.md | 132 ++++++++ .../development/accessibility-audit/SKILL.md | 134 ++++++++ .../development/alerting-strategy/SKILL.md | 134 ++++++++ .../skills/development/api-design/SKILL.md | 134 ++++++++ .../api-documentation-writer/SKILL.md | 134 ++++++++ .../development/api-gateway-design/SKILL.md | 134 ++++++++ .../api-versioning-strategy/SKILL.md | 134 ++++++++ .../architecture-decision-record/SKILL.md | 134 ++++++++ .../architecture-overview/SKILL.md | 134 ++++++++ .../blue-green-deployment/SKILL.md | 134 ++++++++ .../development/branching-strategy/SKILL.md | 134 ++++++++ .../development/caching-strategy/SKILL.md | 134 ++++++++ .../development/canary-deployment/SKILL.md | 134 ++++++++ .../development/ci-cd-pipeline/SKILL.md | 134 ++++++++ .../circuit-breaker-pattern/SKILL.md | 134 ++++++++ .../skills/development/code-cleanup/SKILL.md | 134 ++++++++ .../code-review-checklist/SKILL.md | 134 ++++++++ .../development/codebase-walkthrough/SKILL.md | 134 ++++++++ .../development/coding-standards/SKILL.md | 134 ++++++++ .../development/commit-message-guide/SKILL.md | 134 ++++++++ .../development/contributing-guide/SKILL.md | 134 ++++++++ .../cross-browser-testing/SKILL.md | 134 ++++++++ .../data-model-documentation/SKILL.md | 134 ++++++++ .../database-schema-design/SKILL.md | 134 ++++++++ .../development/dependency-audit/SKILL.md | 134 ++++++++ .../development/deployment-checklist/SKILL.md | 134 ++++++++ .../dev-environment-parity/SKILL.md | 134 ++++++++ .../development/developer-onboarding/SKILL.md | 134 ++++++++ .../development/distributed-tracing/SKILL.md | 134 ++++++++ .../skills/development/docker-setup/SKILL.md | 134 ++++++++ .../documentation-standard/SKILL.md | 134 ++++++++ .../development/e2e-test-strategy/SKILL.md | 134 ++++++++ .../development/environment-setup/SKILL.md | 134 ++++++++ .../development/error-handling-guide/SKILL.md | 134 ++++++++ .../event-driven-architecture/SKILL.md | 134 ++++++++ .../feature-flag-implementation/SKILL.md | 134 ++++++++ .../skills/development/git-workflow/SKILL.md | 134 ++++++++ .../development/incident-response/SKILL.md | 134 ++++++++ .../infrastructure-as-code/SKILL.md | 134 ++++++++ .../integration-test-plan/SKILL.md | 134 ++++++++ .../kubernetes-deployment/SKILL.md | 134 ++++++++ .../development/license-compliance/SKILL.md | 134 ++++++++ .../skills/development/linting-setup/SKILL.md | 134 ++++++++ .../development/load-test-plan/SKILL.md | 134 ++++++++ .../development/local-dev-setup/SKILL.md | 134 ++++++++ .../development/logging-strategy/SKILL.md | 134 ++++++++ .../development/microservices-design/SKILL.md | 134 ++++++++ .../development/migration-script/SKILL.md | 134 ++++++++ .../development/monitoring-setup/SKILL.md | 134 ++++++++ .../development/observability-setup/SKILL.md | 134 ++++++++ .../development/on-call-runbook/SKILL.md | 134 ++++++++ .../open-source-checklist/SKILL.md | 134 ++++++++ .../optimization-checklist/SKILL.md | 134 ++++++++ .../development/package-publishing/SKILL.md | 134 ++++++++ .../performance-profiling/SKILL.md | 134 ++++++++ .../development/postmortem-template/SKILL.md | 134 ++++++++ .../development/pre-commit-hooks/SKILL.md | 134 ++++++++ .../pull-request-template/SKILL.md | 134 ++++++++ .../skills/development/queue-design/SKILL.md | 134 ++++++++ .../development/readme-template/SKILL.md | 134 ++++++++ .../development/refactoring-plan/SKILL.md | 134 ++++++++ .../development/release-management/SKILL.md | 134 ++++++++ .../responsive-design-checklist/SKILL.md | 134 ++++++++ .../development/retry-strategy/SKILL.md | 134 ++++++++ .../skills/development/rollback-plan/SKILL.md | 134 ++++++++ .../development/root-cause-analysis/SKILL.md | 134 ++++++++ .../development/security-checklist/SKILL.md | 134 ++++++++ .../development/security-review/SKILL.md | 134 ++++++++ .../development/semantic-versioning/SKILL.md | 134 ++++++++ .../development/service-boundary/SKILL.md | 134 ++++++++ .../supply-chain-security/SKILL.md | 134 ++++++++ .../development/system-design-doc/SKILL.md | 134 ++++++++ .../development/tech-debt-inventory/SKILL.md | 134 ++++++++ .../development/technical-spec/SKILL.md | 134 ++++++++ .../test-coverage-analysis/SKILL.md | 134 ++++++++ .../skills/development/test-plan/SKILL.md | 134 ++++++++ .../development/testing-pyramid/SKILL.md | 134 ++++++++ .../development/unit-test-writer/SKILL.md | 134 ++++++++ .../vulnerability-assessment/SKILL.md | 134 ++++++++ .../skills/ecommerce/amazon-listing/SKILL.md | 132 ++++++++ .../ecommerce/amazon-ppc-strategy/SKILL.md | 132 ++++++++ .../ecommerce/black-friday-strategy/SKILL.md | 132 ++++++++ .../skills/ecommerce/bundle-strategy/SKILL.md | 132 ++++++++ .../cart-abandonment-analysis/SKILL.md | 132 ++++++++ .../ecommerce/category-taxonomy/SKILL.md | 132 ++++++++ .../ecommerce/checkout-optimization/SKILL.md | 132 ++++++++ .../ecommerce/collection-page-design/SKILL.md | 132 ++++++++ .../ecommerce/conversion-rate-audit/SKILL.md | 132 ++++++++ .../ecommerce/cross-border-ecommerce/SKILL.md | 132 ++++++++ .../customer-acquisition-cost/SKILL.md | 132 ++++++++ .../customer-lifetime-value/SKILL.md | 132 ++++++++ .../customer-review-strategy/SKILL.md | 132 ++++++++ .../customer-segmentation-ecom/SKILL.md | 132 ++++++++ .../ecommerce/dead-stock-analysis/SKILL.md | 132 ++++++++ .../ecommerce/dropshipping-setup/SKILL.md | 132 ++++++++ .../ecommerce/dynamic-pricing-model/SKILL.md | 132 ++++++++ .../ecommerce/ecommerce-analytics/SKILL.md | 132 ++++++++ .../ecommerce/email-marketing-ecom/SKILL.md | 132 ++++++++ .../skills/ecommerce/etsy-listing/SKILL.md | 132 ++++++++ .../skills/ecommerce/flash-sale-plan/SKILL.md | 132 ++++++++ .../fulfillment-optimization/SKILL.md | 132 ++++++++ .../ecommerce/inventory-forecasting/SKILL.md | 132 ++++++++ .../landing-page-optimization/SKILL.md | 132 ++++++++ .../ecommerce/localization-checklist/SKILL.md | 132 ++++++++ .../ecommerce/loyalty-program-design/SKILL.md | 132 ++++++++ .../ecommerce/marketplace-strategy/SKILL.md | 132 ++++++++ .../multi-currency-strategy/SKILL.md | 132 ++++++++ .../personalization-strategy/SKILL.md | 132 ++++++++ .../ecommerce/pricing-strategy-ecom/SKILL.md | 132 ++++++++ .../product-description-writer/SKILL.md | 132 ++++++++ .../skills/ecommerce/product-listing/SKILL.md | 132 ++++++++ .../product-page-optimization/SKILL.md | 132 ++++++++ .../product-performance-analysis/SKILL.md | 132 ++++++++ .../product-photography-brief/SKILL.md | 132 ++++++++ .../product-title-optimization/SKILL.md | 132 ++++++++ .../ecommerce/product-video-brief/SKILL.md | 132 ++++++++ .../push-notification-strategy/SKILL.md | 132 ++++++++ .../ecommerce/recommendation-engine/SKILL.md | 132 ++++++++ .../returns-policy-optimization/SKILL.md | 132 ++++++++ .../review-response-template/SKILL.md | 132 ++++++++ .../skills/ecommerce/sales-report/SKILL.md | 132 ++++++++ .../ecommerce/seasonal-planning/SKILL.md | 132 ++++++++ .../ecommerce/shipping-strategy/SKILL.md | 132 ++++++++ .../ecommerce/shopify-optimization/SKILL.md | 132 ++++++++ .../ecommerce/sms-marketing-ecom/SKILL.md | 132 ++++++++ .../ecommerce/social-proof-strategy/SKILL.md | 132 ++++++++ .../stock-level-optimization/SKILL.md | 132 ++++++++ .../ecommerce/subscription-model/SKILL.md | 132 ++++++++ .../ecommerce/supplier-evaluation/SKILL.md | 132 ++++++++ .../ecommerce/unit-economics-ecom/SKILL.md | 132 ++++++++ .../skills/ecommerce/vip-program/SKILL.md | 132 ++++++++ .../ecommerce/wholesale-strategy/SKILL.md | 132 ++++++++ .../ecommerce/woocommerce-setup/SKILL.md | 132 ++++++++ .../education/assessment-design/SKILL.md | 132 ++++++++ .../skills/education/badge-system/SKILL.md | 132 ++++++++ .../education/case-study-teaching/SKILL.md | 132 ++++++++ .../certification-program-design/SKILL.md | 132 ++++++++ .../education/coaching-program/SKILL.md | 132 ++++++++ .../education/cohort-based-course/SKILL.md | 132 ++++++++ .../education/competency-framework/SKILL.md | 132 ++++++++ .../education/compliance-training/SKILL.md | 132 ++++++++ .../education/content-accessibility/SKILL.md | 132 ++++++++ .../corporate-training-plan/SKILL.md | 132 ++++++++ .../education/course-evaluation/SKILL.md | 132 ++++++++ .../education/course-marketing-plan/SKILL.md | 132 ++++++++ .../skills/education/course-outline/SKILL.md | 132 ++++++++ .../credentialing-framework/SKILL.md | 132 ++++++++ .../education/curriculum-design/SKILL.md | 132 ++++++++ .../customer-service-training/SKILL.md | 132 ++++++++ .../educational-content-review/SKILL.md | 132 ++++++++ .../skills/education/exam-prep/SKILL.md | 132 ++++++++ .../education/leadership-development/SKILL.md | 132 ++++++++ .../education/learning-analytics/SKILL.md | 132 ++++++++ .../education/learning-objectives/SKILL.md | 132 ++++++++ .../skills/education/learning-path/SKILL.md | 132 ++++++++ .../skills/education/lesson-plan/SKILL.md | 132 ++++++++ .../education/live-session-plan/SKILL.md | 132 ++++++++ .../education/lms-content-plan/SKILL.md | 132 ++++++++ .../education/management-training/SKILL.md | 132 ++++++++ .../education/mentorship-program/SKILL.md | 132 ++++++++ .../education/microlearning-design/SKILL.md | 132 ++++++++ .../skills/education/module-design/SKILL.md | 132 ++++++++ .../education/office-hours-structure/SKILL.md | 132 ++++++++ .../education/onboarding-training/SKILL.md | 132 ++++++++ .../education/online-course-launch/SKILL.md | 132 ++++++++ .../education/peer-learning-program/SKILL.md | 132 ++++++++ .../skills/education/quiz-generator/SKILL.md | 132 ++++++++ .../education/role-play-scenario-edu/SKILL.md | 132 ++++++++ .../skills/education/rubric-creator/SKILL.md | 132 ++++++++ .../skills/education/sales-training/SKILL.md | 132 ++++++++ .../education/scorm-module-spec/SKILL.md | 132 ++++++++ .../education/simulation-design/SKILL.md | 132 ++++++++ .../education/skills-gap-analysis/SKILL.md | 132 ++++++++ .../education/soft-skills-training/SKILL.md | 132 ++++++++ .../student-feedback-survey/SKILL.md | 132 ++++++++ .../education/student-onboarding/SKILL.md | 132 ++++++++ .../skills/education/study-guide/SKILL.md | 132 ++++++++ .../education/technical-training/SKILL.md | 132 ++++++++ .../training-needs-assessment/SKILL.md | 132 ++++++++ .../skills/education/tutoring-guide/SKILL.md | 132 ++++++++ .../education/universal-design/SKILL.md | 132 ++++++++ .../skills/education/workshop-design/SKILL.md | 132 ++++++++ .../workshop-facilitator-guide/SKILL.md | 132 ++++++++ .../education/workshop-materials/SKILL.md | 132 ++++++++ .../skills/email/announcement-email/SKILL.md | 131 ++++++++ .../browse-abandonment-sequence/SKILL.md | 131 ++++++++ .../skills/email/can-spam-checklist/SKILL.md | 131 ++++++++ .../email/cart-abandonment-sequence/SKILL.md | 131 ++++++++ .../skills/email/cold-outreach-email/SKILL.md | 131 ++++++++ .../skills/email/confirmation-email/SKILL.md | 131 ++++++++ .../email/deliverability-audit/SKILL.md | 131 ++++++++ .../email/domain-reputation-fix/SKILL.md | 131 ++++++++ .../skills/email/email-ab-test-plan/SKILL.md | 131 ++++++++ .../email/email-analytics-dashboard/SKILL.md | 131 ++++++++ .../email/email-automation-workflow/SKILL.md | 131 ++++++++ .../email/email-benchmark-analysis/SKILL.md | 131 ++++++++ .../email/email-compliance-audit/SKILL.md | 131 ++++++++ .../email/email-optimization-audit/SKILL.md | 131 ++++++++ .../email/email-reporting-template/SKILL.md | 131 ++++++++ .../email-segmentation-strategy/SKILL.md | 131 ++++++++ .../email/email-subject-line-testing/SKILL.md | 131 ++++++++ .../email-template-design-brief/SKILL.md | 131 ++++++++ .../email/event-invitation-email/SKILL.md | 131 ++++++++ .../email/feature-launch-email/SKILL.md | 131 ++++++++ .../skills/email/flash-sale-email/SKILL.md | 131 ++++++++ .../email/gdpr-email-checklist/SKILL.md | 131 ++++++++ .../skills/email/html-email-spec/SKILL.md | 131 ++++++++ .../skills/email/launch-sequence/SKILL.md | 131 ++++++++ .../email/lifecycle-email-strategy/SKILL.md | 131 ++++++++ .../skills/email/list-cleaning-plan/SKILL.md | 131 ++++++++ .../newsletter-editorial-calendar/SKILL.md | 131 ++++++++ .../email/newsletter-growth-strategy/SKILL.md | 131 ++++++++ .../skills/email/newsletter-template/SKILL.md | 131 ++++++++ .../skills/email/nurture-sequence/SKILL.md | 131 ++++++++ .../skills/email/onboarding-sequence/SKILL.md | 131 ++++++++ .../email/partnership-outreach-email/SKILL.md | 131 ++++++++ .../email/password-reset-email/SKILL.md | 131 ++++++++ .../skills/email/plain-text-email/SKILL.md | 131 ++++++++ .../email/post-event-follow-up/SKILL.md | 131 ++++++++ .../email/post-purchase-sequence/SKILL.md | 131 ++++++++ .../skills/email/pr-outreach-email/SKILL.md | 131 ++++++++ .../email/product-update-email/SKILL.md | 131 ++++++++ .../skills/email/promotional-email/SKILL.md | 131 ++++++++ .../email/re-engagement-sequence/SKILL.md | 131 ++++++++ .../skills/email/referral-sequence/SKILL.md | 131 ++++++++ .../email/review-request-sequence/SKILL.md | 131 ++++++++ .../skills/email/seasonal-email/SKILL.md | 131 ++++++++ .../skills/email/subscriber-scoring/SKILL.md | 131 ++++++++ .../skills/email/sunset-sequence/SKILL.md | 131 ++++++++ .../email/transactional-email-copy/SKILL.md | 131 ++++++++ .../skills/email/trigger-email-map/SKILL.md | 131 ++++++++ .../skills/email/warm-up-plan/SKILL.md | 131 ++++++++ .../email/webinar-reminder-sequence/SKILL.md | 131 ++++++++ .../skills/email/welcome-sequence/SKILL.md | 131 ++++++++ .../skills/email/win-back-sequence/SKILL.md | 131 ++++++++ .../skills/energy/adaptation-plan/SKILL.md | 131 ++++++++ .../energy/battery-storage-analysis/SKILL.md | 131 ++++++++ .../carbon-footprint-calculator/SKILL.md | 131 ++++++++ .../energy/carbon-offset-strategy/SKILL.md | 131 ++++++++ .../circular-economy-assessment/SKILL.md | 131 ++++++++ .../energy/climate-risk-assessment/SKILL.md | 131 ++++++++ .../skills/energy/community-impact/SKILL.md | 131 ++++++++ .../energy/conservation-strategy/SKILL.md | 131 ++++++++ .../skills/energy/energy-audit/SKILL.md | 131 ++++++++ .../energy/energy-management-system/SKILL.md | 131 ++++++++ .../energy/energy-savings-plan/SKILL.md | 131 ++++++++ .../energy/energy-star-certification/SKILL.md | 131 ++++++++ .../energy/environmental-compliance/SKILL.md | 131 ++++++++ .../environmental-impact-assessment/SKILL.md | 131 ++++++++ .../skills/energy/esg-framework/SKILL.md | 131 ++++++++ .../skills/energy/ev-fleet-analysis/SKILL.md | 131 ++++++++ .../skills/energy/ghg-inventory/SKILL.md | 131 ++++++++ .../energy/green-building-checklist/SKILL.md | 131 ++++++++ .../skills/energy/green-marketing/SKILL.md | 131 ++++++++ .../energy/green-vendor-criteria/SKILL.md | 131 ++++++++ .../skills/energy/greenwashing-check/SKILL.md | 131 ++++++++ .../skills/energy/iso-50001-prep/SKILL.md | 131 ++++++++ .../skills/energy/leed-preparation/SKILL.md | 131 ++++++++ .../energy/materiality-assessment/SKILL.md | 131 ++++++++ .../skills/energy/net-zero-plan/SKILL.md | 131 ++++++++ .../skills/energy/permit-tracking/SKILL.md | 131 ++++++++ .../skills/energy/ppa-analysis/SKILL.md | 131 ++++++++ .../skills/energy/recycling-program/SKILL.md | 131 ++++++++ .../renewable-energy-assessment/SKILL.md | 131 ++++++++ .../renewable-energy-certificate/SKILL.md | 131 ++++++++ .../energy/resilience-planning/SKILL.md | 131 ++++++++ .../energy/science-based-targets/SKILL.md | 131 ++++++++ .../skills/energy/scope-3-analysis/SKILL.md | 131 ++++++++ .../skills/energy/social-license/SKILL.md | 131 ++++++++ .../skills/energy/solar-feasibility/SKILL.md | 131 ++++++++ .../stakeholder-engagement-esg/SKILL.md | 131 ++++++++ .../supplier-sustainability-audit/SKILL.md | 131 ++++++++ .../sustainability-communication/SKILL.md | 131 ++++++++ .../energy/sustainability-report-esg/SKILL.md | 131 ++++++++ .../energy/sustainability-strategy/SKILL.md | 131 ++++++++ .../energy/sustainable-procurement/SKILL.md | 131 ++++++++ .../energy/utility-bill-analysis/SKILL.md | 131 ++++++++ .../energy/waste-management-plan/SKILL.md | 131 ++++++++ .../skills/energy/water-audit/SKILL.md | 131 ++++++++ .../skills/energy/water-management/SKILL.md | 131 ++++++++ .../acquisition-due-diligence/SKILL.md | 136 ++++++++ .../finance/balance-sheet-analysis/SKILL.md | 136 ++++++++ .../finance/board-financial-report/SKILL.md | 136 ++++++++ .../skills/finance/bonus-structure/SKILL.md | 136 ++++++++ .../finance/break-even-analysis/SKILL.md | 136 ++++++++ .../skills/finance/budget-template/SKILL.md | 136 ++++++++ .../finance/budget-variance-analysis/SKILL.md | 136 ++++++++ .../.claude/skills/finance/cap-table/SKILL.md | 136 ++++++++ .../finance/cash-flow-forecast/SKILL.md | 136 ++++++++ .../finance/cash-flow-statement/SKILL.md | 136 ++++++++ .../finance/collections-strategy/SKILL.md | 136 ++++++++ .../compensation-benchmarking/SKILL.md | 136 ++++++++ .../competitive-pricing-analysis/SKILL.md | 136 ++++++++ .../finance/compliance-checklist/SKILL.md | 136 ++++++++ .../finance/cost-benefit-analysis/SKILL.md | 136 ++++++++ .../finance/cost-reduction-plan/SKILL.md | 136 ++++++++ .../skills/finance/dcf-valuation/SKILL.md | 136 ++++++++ .../skills/finance/deduction-tracker/SKILL.md | 136 ++++++++ .../deferred-revenue-schedule/SKILL.md | 136 ++++++++ .../finance/depreciation-schedule/SKILL.md | 136 ++++++++ .../skills/finance/expense-policy/SKILL.md | 136 ++++++++ .../finance/expense-report-template/SKILL.md | 136 ++++++++ .../finance/financial-audit-prep/SKILL.md | 136 ++++++++ .../finance/financial-dashboard/SKILL.md | 136 ++++++++ .../skills/finance/financial-model/SKILL.md | 136 ++++++++ .../finance/financial-ratio-analysis/SKILL.md | 136 ++++++++ .../fundraising-financial-model/SKILL.md | 136 ++++++++ .../skills/finance/internal-controls/SKILL.md | 136 ++++++++ .../finance/inventory-valuation/SKILL.md | 136 ++++++++ .../skills/finance/investor-report/SKILL.md | 136 ++++++++ .../skills/finance/invoice-template/SKILL.md | 136 ++++++++ .../skills/finance/kpi-scorecard/SKILL.md | 136 ++++++++ .../skills/finance/management-report/SKILL.md | 136 ++++++++ .../skills/finance/merger-analysis/SKILL.md | 136 ++++++++ .../finance/monte-carlo-simulation/SKILL.md | 136 ++++++++ .../finance/mrr-arr-calculator/SKILL.md | 136 ++++++++ .../skills/finance/npv-irr-analysis/SKILL.md | 136 ++++++++ .../finance/payback-period-analysis/SKILL.md | 136 ++++++++ .../skills/finance/payment-terms/SKILL.md | 136 ++++++++ .../price-sensitivity-analysis/SKILL.md | 136 ++++++++ .../skills/finance/pricing-strategy/SKILL.md | 136 ++++++++ .../finance/procurement-policy/SKILL.md | 136 ++++++++ .../finance/profit-loss-statement/SKILL.md | 136 ++++++++ .../quarterly-financial-review/SKILL.md | 136 ++++++++ .../finance/quarterly-tax-prep/SKILL.md | 136 ++++++++ .../skills/finance/revenue-model/SKILL.md | 136 ++++++++ .../finance/revenue-recognition/SKILL.md | 136 ++++++++ .../skills/finance/roi-analysis/SKILL.md | 136 ++++++++ .../skills/finance/runway-calculator/SKILL.md | 136 ++++++++ .../finance/salary-band-structure/SKILL.md | 136 ++++++++ .../skills/finance/scenario-planning/SKILL.md | 136 ++++++++ .../finance/sensitivity-analysis/SKILL.md | 136 ++++++++ .../finance/subscription-cost-audit/SKILL.md | 136 ++++++++ .../skills/finance/synergy-model/SKILL.md | 136 ++++++++ .../finance/tax-planning-checklist/SKILL.md | 136 ++++++++ .../finance/term-sheet-analysis/SKILL.md | 136 ++++++++ .../finance/unit-economics-model/SKILL.md | 136 ++++++++ .../finance/vendor-payment-analysis/SKILL.md | 136 ++++++++ .../finance/working-capital-analysis/SKILL.md | 136 ++++++++ .../skills/finance/zero-based-budget/SKILL.md | 136 ++++++++ .../fitness-wellness/app-programming/SKILL.md | 132 ++++++++ .../body-composition-analysis/SKILL.md | 132 ++++++++ .../bootcamp-program/SKILL.md | 132 ++++++++ .../breathwork-session/SKILL.md | 132 ++++++++ .../certification-prep/SKILL.md | 132 ++++++++ .../fitness-wellness/class-design/SKILL.md | 132 ++++++++ .../cleaning-protocol/SKILL.md | 132 ++++++++ .../client-assessment/SKILL.md | 132 ++++++++ .../client-onboarding-fitness/SKILL.md | 132 ++++++++ .../client-retention-fitness/SKILL.md | 132 ++++++++ .../content-plan-fitness/SKILL.md | 132 ++++++++ .../continuing-education-plan/SKILL.md | 132 ++++++++ .../corporate-wellness-program/SKILL.md | 132 ++++++++ .../equipment-maintenance-fitness/SKILL.md | 132 ++++++++ .../fitness-business-plan/SKILL.md | 132 ++++++++ .../fitness-wellness/fitness-test/SKILL.md | 132 ++++++++ .../goal-setting-fitness/SKILL.md | 132 ++++++++ .../group-fitness-plan/SKILL.md | 132 ++++++++ .../habit-change-program/SKILL.md | 132 ++++++++ .../injury-prevention/SKILL.md | 132 ++++++++ .../fitness-wellness/meal-plan/SKILL.md | 132 ++++++++ .../meditation-guide/SKILL.md | 132 ++++++++ .../membership-model/SKILL.md | 132 ++++++++ .../fitness-wellness/nutrition-plan/SKILL.md | 132 ++++++++ .../online-coaching-setup/SKILL.md | 132 ++++++++ .../periodization-plan/SKILL.md | 132 ++++++++ .../fitness-wellness/pricing-fitness/SKILL.md | 132 ++++++++ .../progress-tracking/SKILL.md | 132 ++++++++ .../referral-program-fitness/SKILL.md | 132 ++++++++ .../rehab-protocol-guide/SKILL.md | 132 ++++++++ .../retreat-planning/SKILL.md | 132 ++++++++ .../fitness-wellness/return-to-sport/SKILL.md | 132 ++++++++ .../social-media-fitness/SKILL.md | 132 ++++++++ .../specialization-track/SKILL.md | 132 ++++++++ .../stress-management/SKILL.md | 132 ++++++++ .../studio-operations/SKILL.md | 132 ++++++++ .../supplement-guide/SKILL.md | 132 ++++++++ .../testimonial-collection/SKILL.md | 132 ++++++++ .../fitness-wellness/training-plan/SKILL.md | 132 ++++++++ .../transformation-story/SKILL.md | 132 ++++++++ .../virtual-training-guide/SKILL.md | 132 ++++++++ .../wellness-coaching-plan/SKILL.md | 132 ++++++++ .../fitness-wellness/workout-program/SKILL.md | 132 ++++++++ .../workshop-fitness/SKILL.md | 132 ++++++++ .../fitness-wellness/yoga-sequence/SKILL.md | 132 ++++++++ .../allergen-management/SKILL.md | 131 ++++++++ .../food-beverage/bar-training/SKILL.md | 131 ++++++++ .../food-beverage/brand-standards/SKILL.md | 131 ++++++++ .../food-beverage/catering-proposal/SKILL.md | 131 ++++++++ .../food-beverage/cocktail-menu/SKILL.md | 131 ++++++++ .../concept-development/SKILL.md | 131 ++++++++ .../cross-training-plan/SKILL.md | 131 ++++++++ .../customer-feedback-restaurant/SKILL.md | 131 ++++++++ .../delivery-optimization/SKILL.md | 131 ++++++++ .../event-menu-planning/SKILL.md | 131 ++++++++ .../food-beverage/food-cost-analysis/SKILL.md | 131 ++++++++ .../food-beverage/food-safety-plan/SKILL.md | 131 ++++++++ .../franchise-operations-manual/SKILL.md | 131 ++++++++ .../skills/food-beverage/haccp-plan/SKILL.md | 131 ++++++++ .../health-inspection-prep/SKILL.md | 131 ++++++++ .../food-beverage/influencer-dining/SKILL.md | 131 ++++++++ .../ingredient-sourcing/SKILL.md | 131 ++++++++ .../inventory-management-restaurant/SKILL.md | 131 ++++++++ .../food-beverage/labor-scheduling/SKILL.md | 131 ++++++++ .../loyalty-program-restaurant/SKILL.md | 131 ++++++++ .../food-beverage/market-feasibility/SKILL.md | 131 ++++++++ .../marketing-restaurant/SKILL.md | 131 ++++++++ .../food-beverage/menu-costing/SKILL.md | 131 ++++++++ .../skills/food-beverage/menu-design/SKILL.md | 131 ++++++++ .../food-beverage/menu-engineering/SKILL.md | 131 ++++++++ .../online-ordering-setup/SKILL.md | 131 ++++++++ .../food-beverage/opening-checklist/SKILL.md | 131 ++++++++ .../food-beverage/par-level-setting/SKILL.md | 131 ++++++++ .../food-beverage/peak-hour-planning/SKILL.md | 131 ++++++++ .../food-beverage/portion-control/SKILL.md | 131 ++++++++ .../food-beverage/recipe-scaling/SKILL.md | 131 ++++++++ .../recipe-standardization/SKILL.md | 131 ++++++++ .../restaurant-business-plan/SKILL.md | 131 ++++++++ .../review-management-restaurant/SKILL.md | 131 ++++++++ .../sanitation-checklist/SKILL.md | 131 ++++++++ .../food-beverage/service-standards/SKILL.md | 131 ++++++++ .../social-media-restaurant/SKILL.md | 131 ++++++++ .../staff-training-restaurant/SKILL.md | 131 ++++++++ .../food-beverage/temperature-log/SKILL.md | 131 ++++++++ .../food-beverage/vendor-negotiation/SKILL.md | 131 ++++++++ .../food-beverage/waste-reduction/SKILL.md | 131 ++++++++ .../food-beverage/wine-pairing/SKILL.md | 131 ++++++++ .../healthcare/appointment-reminder/SKILL.md | 132 ++++++++ .../skills/healthcare/billing-audit/SKILL.md | 132 ++++++++ .../healthcare/breach-response/SKILL.md | 132 ++++++++ .../healthcare/care-coordination/SKILL.md | 132 ++++++++ .../skills/healthcare/care-plan/SKILL.md | 132 ++++++++ .../chronic-disease-management/SKILL.md | 132 ++++++++ .../clinical-trial-recruitment/SKILL.md | 132 ++++++++ .../healthcare/coding-accuracy/SKILL.md | 132 ++++++++ .../healthcare/condition-explainer/SKILL.md | 132 ++++++++ .../skills/healthcare/consent-form/SKILL.md | 132 ++++++++ .../healthcare/corporate-wellness/SKILL.md | 132 ++++++++ .../credentialing-checklist/SKILL.md | 132 ++++++++ .../discharge-instructions/SKILL.md | 132 ++++++++ .../healthcare/follow-up-message/SKILL.md | 132 ++++++++ .../health-content-article/SKILL.md | 132 ++++++++ .../hipaa-compliance-checklist/SKILL.md | 132 ++++++++ .../healthcare/infection-control/SKILL.md | 132 ++++++++ .../healthcare/informed-consent/SKILL.md | 132 ++++++++ .../insurance-verification/SKILL.md | 132 ++++++++ .../healthcare/medical-history-form/SKILL.md | 132 ++++++++ .../mental-health-resources-health/SKILL.md | 132 ++++++++ .../online-reputation-management/SKILL.md | 132 ++++++++ .../healthcare/patient-acquisition/SKILL.md | 132 ++++++++ .../healthcare/patient-communication/SKILL.md | 132 ++++++++ .../patient-education-material/SKILL.md | 132 ++++++++ .../healthcare/patient-intake-form/SKILL.md | 132 ++++++++ .../healthcare/patient-portal-guide/SKILL.md | 132 ++++++++ .../patient-satisfaction-survey/SKILL.md | 132 ++++++++ .../population-health-report/SKILL.md | 132 ++++++++ .../healthcare/practice-dashboard/SKILL.md | 132 ++++++++ .../practice-marketing-plan/SKILL.md | 132 ++++++++ .../healthcare/preventive-care-plan/SKILL.md | 132 ++++++++ .../skills/healthcare/privacy-notice/SKILL.md | 132 ++++++++ .../healthcare/provider-enrollment/SKILL.md | 132 ++++++++ .../healthcare/quality-metrics/SKILL.md | 132 ++++++++ .../healthcare/referral-management/SKILL.md | 132 ++++++++ .../referral-program-health/SKILL.md | 132 ++++++++ .../research-protocol-summary/SKILL.md | 132 ++++++++ .../revenue-cycle-optimization/SKILL.md | 132 ++++++++ .../review-response-healthcare/SKILL.md | 132 ++++++++ .../healthcare/safety-protocol/SKILL.md | 132 ++++++++ .../staff-training-healthcare/SKILL.md | 132 ++++++++ .../healthcare/telehealth-setup/SKILL.md | 132 ++++++++ .../testimonial-request-health/SKILL.md | 132 ++++++++ .../healthcare/transition-of-care/SKILL.md | 132 ++++++++ .../treatment-plan-template/SKILL.md | 132 ++++++++ .../healthcare/virtual-visit-guide/SKILL.md | 132 ++++++++ .../healthcare/wellness-program/SKILL.md | 132 ++++++++ .../.claude/skills/hr/30-60-90-plan/SKILL.md | 133 ++++++++ .../skills/hr/all-hands-agenda/SKILL.md | 133 ++++++++ .../skills/hr/attrition-analysis/SKILL.md | 133 ++++++++ .../skills/hr/benefits-comparison/SKILL.md | 133 ++++++++ .../skills/hr/buddy-system-guide/SKILL.md | 133 ++++++++ .../skills/hr/candidate-evaluation/SKILL.md | 133 ++++++++ .../hr/career-development-plan/SKILL.md | 133 ++++++++ .../skills/hr/coaching-conversation/SKILL.md | 133 ++++++++ .../skills/hr/compensation-review/SKILL.md | 133 ++++++++ .../skills/hr/conflict-resolution/SKILL.md | 133 ++++++++ .../skills/hr/contractor-management/SKILL.md | 133 ++++++++ .../.claude/skills/hr/culture-deck/SKILL.md | 133 ++++++++ .../hr/culture-values-definition/SKILL.md | 133 ++++++++ .../.claude/skills/hr/dei-metrics/SKILL.md | 133 ++++++++ .../.claude/skills/hr/dei-strategy/SKILL.md | 133 ++++++++ .../hr/employee-engagement-survey/SKILL.md | 133 ++++++++ .../skills/hr/employee-handbook/SKILL.md | 133 ++++++++ .../.claude/skills/hr/employer-brand/SKILL.md | 133 ++++++++ .../.claude/skills/hr/exit-interview/SKILL.md | 133 ++++++++ .../skills/hr/feedback-framework/SKILL.md | 133 ++++++++ .../skills/hr/grievance-procedure/SKILL.md | 133 ++++++++ .../.claude/skills/hr/hiring-plan/SKILL.md | 133 ++++++++ .../.claude/skills/hr/hr-dashboard/SKILL.md | 133 ++++++++ .../skills/hr/hybrid-work-policy/SKILL.md | 133 ++++++++ .../skills/hr/inclusive-hiring-guide/SKILL.md | 133 ++++++++ .../hr/individual-development-plan/SKILL.md | 133 ++++++++ .../hr/interview-question-bank/SKILL.md | 133 ++++++++ .../skills/hr/interview-scorecard/SKILL.md | 133 ++++++++ .../skills/hr/job-description/SKILL.md | 133 ++++++++ .../hr/job-posting-optimization/SKILL.md | 133 ++++++++ .../skills/hr/mediation-guide/SKILL.md | 133 ++++++++ .../hr/mental-health-resources/SKILL.md | 133 ++++++++ .../hr/offer-negotiation-guide/SKILL.md | 133 ++++++++ .../skills/hr/offsite-planning/SKILL.md | 133 ++++++++ .../skills/hr/onboarding-program/SKILL.md | 133 ++++++++ .../skills/hr/organizational-design/SKILL.md | 133 ++++++++ .../skills/hr/peer-review-template/SKILL.md | 133 ++++++++ .../skills/hr/people-analytics/SKILL.md | 133 ++++++++ .../skills/hr/performance-review/SKILL.md | 133 ++++++++ .../.claude/skills/hr/pip-plan/SKILL.md | 133 ++++++++ .../.claude/skills/hr/pulse-survey/SKILL.md | 133 ++++++++ .../skills/hr/recognition-program/SKILL.md | 133 ++++++++ .../skills/hr/reference-check-guide/SKILL.md | 133 ++++++++ .../skills/hr/remote-work-policy/SKILL.md | 133 ++++++++ .../skills/hr/role-definition/SKILL.md | 133 ++++++++ .../hr/salary-negotiation-guide/SKILL.md | 133 ++++++++ .../skills/hr/self-assessment/SKILL.md | 133 ++++++++ .../hr/structured-interview-guide/SKILL.md | 133 ++++++++ .../skills/hr/succession-planning/SKILL.md | 133 ++++++++ .../skills/hr/team-building-activity/SKILL.md | 133 ++++++++ .../.claude/skills/hr/team-structure/SKILL.md | 133 ++++++++ .../skills/hr/temp-to-perm-process/SKILL.md | 133 ++++++++ .../hr/training-needs-analysis/SKILL.md | 133 ++++++++ .../hr/training-program-design/SKILL.md | 133 ++++++++ .../skills/hr/wellness-program/SKILL.md | 133 ++++++++ .../skills/hr/workforce-planning/SKILL.md | 133 ++++++++ .../hr/workshop-facilitator-guide/SKILL.md | 133 ++++++++ .../legal/acceptable-use-policy/SKILL.md | 131 ++++++++ .../legal/annual-report-compliance/SKILL.md | 131 ++++++++ .../skills/legal/anti-bribery-policy/SKILL.md | 131 ++++++++ .../skills/legal/audit-response/SKILL.md | 131 ++++++++ .../skills/legal/board-resolution/SKILL.md | 131 ++++++++ .../skills/legal/breach-notification/SKILL.md | 131 ++++++++ .../skills/legal/bylaws-template/SKILL.md | 131 ++++++++ .../legal/ccpa-compliance-checklist/SKILL.md | 131 ++++++++ .../skills/legal/cease-and-desist/SKILL.md | 131 ++++++++ .../skills/legal/code-of-conduct/SKILL.md | 131 ++++++++ .../skills/legal/compliance-program/SKILL.md | 131 ++++++++ .../compliance-training-outline/SKILL.md | 131 ++++++++ .../conflict-of-interest-policy/SKILL.md | 131 ++++++++ .../skills/legal/consent-resolution/SKILL.md | 131 ++++++++ .../legal/contractor-agreement/SKILL.md | 131 ++++++++ .../skills/legal/cookie-policy/SKILL.md | 131 ++++++++ .../skills/legal/copyright-notice/SKILL.md | 131 ++++++++ .../legal/data-processing-agreement/SKILL.md | 131 ++++++++ .../legal/data-retention-policy/SKILL.md | 131 ++++++++ .../skills/legal/demand-letter/SKILL.md | 131 ++++++++ .../.claude/skills/legal/dmca-policy/SKILL.md | 131 ++++++++ .../skills/legal/dpia-template/SKILL.md | 131 ++++++++ .../legal/employment-agreement/SKILL.md | 131 ++++++++ .../legal/gdpr-compliance-audit/SKILL.md | 131 ++++++++ .../skills/legal/gdpr-data-mapping/SKILL.md | 131 ++++++++ .../legal/incident-response-plan/SKILL.md | 131 ++++++++ .../legal/insider-trading-policy/SKILL.md | 131 ++++++++ .../skills/legal/insurance-review/SKILL.md | 131 ++++++++ .../legal/ip-assignment-agreement/SKILL.md | 131 ++++++++ .../legal/joint-venture-agreement/SKILL.md | 131 ++++++++ .../legal/lease-review-checklist/SKILL.md | 131 ++++++++ .../skills/legal/licensing-agreement/SKILL.md | 131 ++++++++ .../skills/legal/litigation-hold/SKILL.md | 131 ++++++++ .../skills/legal/meeting-minutes/SKILL.md | 131 ++++++++ .../skills/legal/mou-template/SKILL.md | 131 ++++++++ .../skills/legal/nda-generator/SKILL.md | 131 ++++++++ .../skills/legal/offer-letter/SKILL.md | 131 ++++++++ .../skills/legal/operating-agreement/SKILL.md | 131 ++++++++ .../legal/partnership-agreement/SKILL.md | 131 ++++++++ .../legal/patent-prior-art-search/SKILL.md | 131 ++++++++ .../skills/legal/privacy-policy/SKILL.md | 131 ++++++++ .../skills/legal/refund-policy/SKILL.md | 131 ++++++++ .../legal/regulatory-change-tracker/SKILL.md | 131 ++++++++ .../regulatory-filing-checklist/SKILL.md | 131 ++++++++ .../skills/legal/risk-assessment/SKILL.md | 131 ++++++++ .../skills/legal/service-agreement/SKILL.md | 131 ++++++++ .../legal/settlement-agreement/SKILL.md | 131 ++++++++ .../legal/shareholder-agreement/SKILL.md | 131 ++++++++ .../skills/legal/shipping-policy/SKILL.md | 131 ++++++++ .../skills/legal/termination-letter/SKILL.md | 131 ++++++++ .../skills/legal/terms-of-service/SKILL.md | 131 ++++++++ .../legal/trademark-filing-guide/SKILL.md | 131 ++++++++ .../legal/vendor-contract-review/SKILL.md | 131 ++++++++ .../legal/whistleblower-policy/SKILL.md | 131 ++++++++ .../account-based-marketing/SKILL.md | 138 ++++++++ .../marketing/attribution-model/SKILL.md | 138 ++++++++ .../marketing/audience-persona/SKILL.md | 138 ++++++++ .../marketing/audience-segmentation/SKILL.md | 138 ++++++++ .../marketing/b2b-marketing-plan/SKILL.md | 138 ++++++++ .../marketing/b2c-marketing-plan/SKILL.md | 138 ++++++++ .../back-to-school-campaign/SKILL.md | 138 ++++++++ .../skills/marketing/brand-audit/SKILL.md | 138 ++++++++ .../marketing/brand-guidelines/SKILL.md | 138 ++++++++ .../brand-messaging-framework/SKILL.md | 138 ++++++++ .../marketing/brand-positioning/SKILL.md | 138 ++++++++ .../marketing/brand-voice-guide/SKILL.md | 138 ++++++++ .../skills/marketing/campaign-brief/SKILL.md | 138 ++++++++ .../marketing/campaign-retrospective/SKILL.md | 138 ++++++++ .../marketing/campaign-strategy/SKILL.md | 138 ++++++++ .../channel-mix-optimization/SKILL.md | 138 ++++++++ .../marketing/channel-strategy/SKILL.md | 138 ++++++++ .../marketing/co-marketing-plan/SKILL.md | 138 ++++++++ .../marketing/community-strategy/SKILL.md | 138 ++++++++ .../marketing/competitor-ad-teardown/SKILL.md | 138 ++++++++ .../marketing/competitor-analysis/SKILL.md | 138 ++++++++ .../content-marketing-strategy/SKILL.md | 138 ++++++++ .../conversion-funnel-analysis/SKILL.md | 138 ++++++++ .../crisis-communication-plan/SKILL.md | 138 ++++++++ .../cross-promotion-strategy/SKILL.md | 138 ++++++++ .../marketing/customer-journey-map/SKILL.md | 138 ++++++++ .../skills/marketing/d2c-strategy/SKILL.md | 138 ++++++++ .../marketing/demand-generation/SKILL.md | 138 ++++++++ .../marketing/drip-campaign-design/SKILL.md | 138 ++++++++ .../skills/marketing/elevator-pitch/SKILL.md | 138 ++++++++ .../marketing/event-marketing-plan/SKILL.md | 138 ++++++++ .../marketing/geo-targeting-strategy/SKILL.md | 138 ++++++++ .../marketing/go-to-market-plan/SKILL.md | 138 ++++++++ .../marketing/growth-experiment/SKILL.md | 138 ++++++++ .../marketing/guerrilla-marketing/SKILL.md | 138 ++++++++ .../marketing/holiday-marketing-plan/SKILL.md | 138 ++++++++ .../marketing/influencer-brief/SKILL.md | 138 ++++++++ .../marketing/influencer-outreach/SKILL.md | 138 ++++++++ .../marketing/influencer-strategy/SKILL.md | 138 ++++++++ .../skills/marketing/kpi-framework/SKILL.md | 138 ++++++++ .../marketing/launch-checklist/SKILL.md | 138 ++++++++ .../skills/marketing/launch-timeline/SKILL.md | 138 ++++++++ .../marketing/lead-magnet-strategy/SKILL.md | 138 ++++++++ .../marketing/local-marketing-plan/SKILL.md | 138 ++++++++ .../skills/marketing/loyalty-program/SKILL.md | 138 ++++++++ .../skills/marketing/market-research/SKILL.md | 138 ++++++++ .../skills/marketing/market-sizing/SKILL.md | 138 ++++++++ .../marketing-automation-setup/SKILL.md | 138 ++++++++ .../marketing/marketing-budget/SKILL.md | 138 ++++++++ .../marketing/marketing-calendar/SKILL.md | 138 ++++++++ .../marketing/marketing-dashboard/SKILL.md | 138 ++++++++ .../marketing-funnel-design/SKILL.md | 138 ++++++++ .../marketing/marketing-stack-audit/SKILL.md | 138 ++++++++ .../marketing/martech-evaluation/SKILL.md | 138 ++++++++ .../skills/marketing/media-kit/SKILL.md | 138 ++++++++ .../skills/marketing/media-pitch/SKILL.md | 138 ++++++++ .../marketing/messaging-matrix/SKILL.md | 138 ++++++++ .../marketing/multi-market-launch/SKILL.md | 138 ++++++++ .../marketing/partnership-strategy/SKILL.md | 138 ++++++++ .../skills/marketing/pr-strategy/SKILL.md | 138 ++++++++ .../skills/marketing/press-release/SKILL.md | 138 ++++++++ .../marketing/product-launch-plan/SKILL.md | 138 ++++++++ .../skills/marketing/rebranding-plan/SKILL.md | 138 ++++++++ .../marketing/referral-program/SKILL.md | 138 ++++++++ .../marketing/retargeting-strategy/SKILL.md | 138 ++++++++ .../marketing/seasonal-campaign/SKILL.md | 138 ++++++++ .../marketing/sponsorship-proposal/SKILL.md | 138 ++++++++ .../marketing/tagline-generator/SKILL.md | 138 ++++++++ .../thought-leadership-plan/SKILL.md | 138 ++++++++ .../marketing/touchpoint-audit/SKILL.md | 138 ++++++++ .../marketing/trade-show-strategy/SKILL.md | 138 ++++++++ .../unique-selling-proposition/SKILL.md | 138 ++++++++ .../value-proposition-canvas/SKILL.md | 138 ++++++++ .../marketing/vendor-comparison/SKILL.md | 138 ++++++++ .../marketing/viral-loop-design/SKILL.md | 138 ++++++++ .../skills/marketing/webinar-plan/SKILL.md | 138 ++++++++ .../media/advertising-rate-card/SKILL.md | 132 ++++++++ .../skills/media/article-outline/SKILL.md | 132 ++++++++ .../media/audience-growth-strategy/SKILL.md | 132 ++++++++ .../skills/media/audience-insights/SKILL.md | 132 ++++++++ .../skills/media/book-outline/SKILL.md | 132 ++++++++ .../skills/media/book-proposal/SKILL.md | 132 ++++++++ .../media/breaking-news-protocol/SKILL.md | 132 ++++++++ .../skills/media/chapter-outline/SKILL.md | 132 ++++++++ .../media/content-analytics-report/SKILL.md | 132 ++++++++ .../media/content-distribution/SKILL.md | 132 ++++++++ .../skills/media/content-licensing/SKILL.md | 132 ++++++++ .../skills/media/content-performance/SKILL.md | 132 ++++++++ .../media/content-strategy-media/SKILL.md | 132 ++++++++ .../skills/media/content-syndication/SKILL.md | 132 ++++++++ .../media/contributor-guidelines/SKILL.md | 132 ++++++++ .../skills/media/correction-policy/SKILL.md | 132 ++++++++ .../skills/media/cross-promotion/SKILL.md | 132 ++++++++ .../skills/media/editorial-calendar/SKILL.md | 132 ++++++++ .../media/editorial-guidelines/SKILL.md | 132 ++++++++ .../media/editorial-style-guide/SKILL.md | 132 ++++++++ .../media/fact-checking-process/SKILL.md | 132 ++++++++ .../skills/media/feature-article/SKILL.md | 132 ++++++++ .../skills/media/freelancer-brief/SKILL.md | 132 ++++++++ .../skills/media/interview-prep/SKILL.md | 132 ++++++++ .../skills/media/interview-questions/SKILL.md | 132 ++++++++ .../media/interview-transcript/SKILL.md | 132 ++++++++ .../skills/media/investigative-piece/SKILL.md | 132 ++++++++ .../.claude/skills/media/live-blog/SKILL.md | 132 ++++++++ .../skills/media/live-event-coverage/SKILL.md | 132 ++++++++ .../skills/media/media-kit-creator/SKILL.md | 132 ++++++++ .../skills/media/newsletter-growth/SKILL.md | 132 ++++++++ .../skills/media/newsletter-launch/SKILL.md | 132 ++++++++ .../media/newsletter-monetization/SKILL.md | 132 ++++++++ .../skills/media/paywall-strategy/SKILL.md | 132 ++++++++ .../media/podcast-format-design/SKILL.md | 132 ++++++++ .../skills/media/podcast-launch-plan/SKILL.md | 132 ++++++++ .../media/podcast-monetization/SKILL.md | 132 ++++++++ .../media/republishing-strategy/SKILL.md | 132 ++++++++ .../media/social-media-promotion/SKILL.md | 132 ++++++++ .../skills/media/sponsorship-deck/SKILL.md | 132 ++++++++ .../skills/media/submission-review/SKILL.md | 132 ++++++++ .../media/subscriber-acquisition/SKILL.md | 132 ++++++++ .../skills/media/video-editing-brief/SKILL.md | 132 ++++++++ .../media/video-production-brief/SKILL.md | 132 ++++++++ .../media/youtube-channel-plan/SKILL.md | 132 ++++++++ .../skills/nonprofit/990-prep/SKILL.md | 131 ++++++++ .../nonprofit/advocacy-campaign/SKILL.md | 131 ++++++++ .../skills/nonprofit/annual-appeal/SKILL.md | 131 ++++++++ .../annual-report-nonprofit/SKILL.md | 131 ++++++++ .../nonprofit/auction-planning/SKILL.md | 131 ++++++++ .../nonprofit/audit-prep-nonprofit/SKILL.md | 131 ++++++++ .../nonprofit/board-meeting-agenda/SKILL.md | 131 ++++++++ .../nonprofit/board-orientation/SKILL.md | 131 ++++++++ .../nonprofit/board-recruitment/SKILL.md | 131 ++++++++ .../nonprofit/case-for-support/SKILL.md | 131 ++++++++ .../skills/nonprofit/cause-marketing/SKILL.md | 131 ++++++++ .../nonprofit/compliance-nonprofit/SKILL.md | 131 ++++++++ .../nonprofit/conflict-of-interest/SKILL.md | 131 ++++++++ .../nonprofit/corporate-partnership/SKILL.md | 131 ++++++++ .../nonprofit/corporate-sponsorship/SKILL.md | 131 ++++++++ .../nonprofit/crowdfunding-campaign/SKILL.md | 131 ++++++++ .../nonprofit/donation-thank-you/SKILL.md | 131 ++++++++ .../nonprofit/donor-cultivation/SKILL.md | 131 ++++++++ .../skills/nonprofit/donor-retention/SKILL.md | 131 ++++++++ .../nonprofit/donor-segmentation/SKILL.md | 131 ++++++++ .../nonprofit/event-fundraiser/SKILL.md | 131 ++++++++ .../financial-report-nonprofit/SKILL.md | 131 ++++++++ .../nonprofit/fundraising-email/SKILL.md | 131 ++++++++ .../nonprofit/fundraising-plan/SKILL.md | 131 ++++++++ .../skills/nonprofit/gala-planning/SKILL.md | 131 ++++++++ .../nonprofit/gift-acceptance-policy/SKILL.md | 131 ++++++++ .../skills/nonprofit/giving-tuesday/SKILL.md | 131 ++++++++ .../skills/nonprofit/grant-budget/SKILL.md | 131 ++++++++ .../skills/nonprofit/grant-proposal/SKILL.md | 131 ++++++++ .../skills/nonprofit/grant-research/SKILL.md | 131 ++++++++ .../grassroots-mobilization/SKILL.md | 131 ++++++++ .../skills/nonprofit/impact-report/SKILL.md | 131 ++++++++ .../lapsed-donor-reactivation/SKILL.md | 131 ++++++++ .../skills/nonprofit/logic-model/SKILL.md | 131 ++++++++ .../nonprofit/major-gift-strategy/SKILL.md | 131 ++++++++ .../nonprofit/needs-assessment/SKILL.md | 131 ++++++++ .../nonprofit-marketing-plan/SKILL.md | 131 ++++++++ .../nonprofit/outcomes-framework/SKILL.md | 131 ++++++++ .../peer-to-peer-fundraising/SKILL.md | 131 ++++++++ .../skills/nonprofit/policy-brief/SKILL.md | 131 ++++++++ .../skills/nonprofit/program-design/SKILL.md | 131 ++++++++ .../nonprofit/program-evaluation/SKILL.md | 131 ++++++++ .../nonprofit/storytelling-nonprofit/SKILL.md | 131 ++++++++ .../strategic-plan-nonprofit/SKILL.md | 131 ++++++++ .../nonprofit/theory-of-change/SKILL.md | 131 ++++++++ .../nonprofit/volunteer-onboarding/SKILL.md | 131 ++++++++ .../nonprofit/volunteer-recognition/SKILL.md | 131 ++++++++ .../nonprofit/volunteer-recruitment/SKILL.md | 131 ++++++++ .../operations/action-item-tracker/SKILL.md | 135 ++++++++ .../automation-opportunity-audit/SKILL.md | 135 ++++++++ .../operations/bottleneck-analysis/SKILL.md | 135 ++++++++ .../business-continuity-plan/SKILL.md | 135 ++++++++ .../operations/capacity-planning/SKILL.md | 135 ++++++++ .../change-management-plan/SKILL.md | 135 ++++++++ .../operations/communication-plan/SKILL.md | 135 ++++++++ .../operations/contingency-plan/SKILL.md | 135 ++++++++ .../cross-functional-alignment/SKILL.md | 135 ++++++++ .../skills/operations/decision-log/SKILL.md | 135 ++++++++ .../operations/defect-tracking/SKILL.md | 135 ++++++++ .../operations/delegation-framework/SKILL.md | 135 ++++++++ .../disaster-recovery-plan/SKILL.md | 135 ++++++++ .../operations/efficiency-audit/SKILL.md | 135 ++++++++ .../operations/executive-summary/SKILL.md | 135 ++++++++ .../operations/goal-setting-workshop/SKILL.md | 135 ++++++++ .../operations/handover-document/SKILL.md | 135 ++++++++ .../operations/incident-management/SKILL.md | 135 ++++++++ .../operations/inventory-management/SKILL.md | 135 ++++++++ .../operations/kanban-board-setup/SKILL.md | 135 ++++++++ .../skills/operations/kpi-definition/SKILL.md | 135 ++++++++ .../skills/operations/lean-six-sigma/SKILL.md | 135 ++++++++ .../operations/lessons-learned/SKILL.md | 135 ++++++++ .../operations/logistics-planning/SKILL.md | 135 ++++++++ .../skills/operations/meeting-agenda/SKILL.md | 135 ++++++++ .../skills/operations/meeting-notes/SKILL.md | 135 ++++++++ .../operations/offboarding-checklist/SKILL.md | 135 ++++++++ .../skills/operations/okr-framework/SKILL.md | 135 ++++++++ .../operations/onboarding-checklist/SKILL.md | 135 ++++++++ .../operations/operating-rhythm/SKILL.md | 135 ++++++++ .../skills/operations/post-mortem/SKILL.md | 135 ++++++++ .../skills/operations/process-map/SKILL.md | 135 ++++++++ .../operations/process-optimization/SKILL.md | 135 ++++++++ .../operations/progress-dashboard/SKILL.md | 135 ++++++++ .../operations/project-charter/SKILL.md | 135 ++++++++ .../skills/operations/project-plan/SKILL.md | 135 ++++++++ .../operations/project-timeline/SKILL.md | 135 ++++++++ .../quality-assurance-plan/SKILL.md | 135 ++++++++ .../operations/quality-checklist/SKILL.md | 135 ++++++++ .../skills/operations/raci-matrix/SKILL.md | 135 ++++++++ .../operations/resource-allocation/SKILL.md | 135 ++++++++ .../responsibility-assignment/SKILL.md | 135 ++++++++ .../operations/risk-mitigation-plan/SKILL.md | 135 ++++++++ .../skills/operations/risk-register/SKILL.md | 135 ++++++++ .../skills/operations/sop-writer/SKILL.md | 135 ++++++++ .../operations/sprint-planning/SKILL.md | 135 ++++++++ .../operations/sprint-retrospective/SKILL.md | 135 ++++++++ .../skills/operations/sprint-review/SKILL.md | 135 ++++++++ .../operations/stakeholder-analysis/SKILL.md | 135 ++++++++ .../skills/operations/status-report/SKILL.md | 135 ++++++++ .../supply-chain-optimization/SKILL.md | 135 ++++++++ .../skills/operations/team-charter/SKILL.md | 135 ++++++++ .../operations/tech-stack-review/SKILL.md | 135 ++++++++ .../time-tracking-analysis/SKILL.md | 135 ++++++++ .../operations/tool-evaluation/SKILL.md | 135 ++++++++ .../operations/vendor-evaluation/SKILL.md | 135 ++++++++ .../operations/vendor-onboarding/SKILL.md | 135 ++++++++ .../operations/vendor-scorecard/SKILL.md | 135 ++++++++ .../operations/workflow-design/SKILL.md | 135 ++++++++ .../operations/workload-balancing/SKILL.md | 135 ++++++++ .../skills/product/ab-test-plan/SKILL.md | 135 ++++++++ .../product/acceptance-criteria/SKILL.md | 135 ++++++++ .../product/activation-checklist/SKILL.md | 135 ++++++++ .../product/aha-moment-analysis/SKILL.md | 135 ++++++++ .../product/analytics-implementation/SKILL.md | 135 ++++++++ .../product/api-product-design/SKILL.md | 135 ++++++++ .../skills/product/beta-program-plan/SKILL.md | 135 ++++++++ .../product/board-product-update/SKILL.md | 135 ++++++++ .../skills/product/bug-triage/SKILL.md | 135 ++++++++ .../skills/product/changelog-writer/SKILL.md | 135 ++++++++ .../competitive-product-analysis/SKILL.md | 135 ++++++++ .../skills/product/data-taxonomy/SKILL.md | 135 ++++++++ .../skills/product/deprecation-plan/SKILL.md | 135 ++++++++ .../product/early-adopter-strategy/SKILL.md | 135 ++++++++ .../skills/product/ecosystem-map/SKILL.md | 135 ++++++++ .../skills/product/empathy-map/SKILL.md | 135 ++++++++ .../product/event-tracking-plan/SKILL.md | 135 ++++++++ .../skills/product/experiment-design/SKILL.md | 135 ++++++++ .../skills/product/faq-builder/SKILL.md | 135 ++++++++ .../feature-comparison-matrix/SKILL.md | 135 ++++++++ .../product/feature-flag-strategy/SKILL.md | 135 ++++++++ .../product/feature-prioritization/SKILL.md | 135 ++++++++ .../product/feature-request-triage/SKILL.md | 135 ++++++++ .../skills/product/feature-roadmap/SKILL.md | 135 ++++++++ .../skills/product/feedback-taxonomy/SKILL.md | 135 ++++++++ .../skills/product/freemium-strategy/SKILL.md | 135 ++++++++ .../product/impact-effort-matrix/SKILL.md | 135 ++++++++ .../skills/product/job-to-be-done/SKILL.md | 135 ++++++++ .../product/knowledge-base-article/SKILL.md | 135 ++++++++ .../skills/product/migration-plan/SKILL.md | 135 ++++++++ .../skills/product/north-star-metric/SKILL.md | 135 ++++++++ .../skills/product/persona-creation/SKILL.md | 135 ++++++++ .../skills/product/pirate-metrics/SKILL.md | 135 ++++++++ .../skills/product/platform-strategy/SKILL.md | 135 ++++++++ .../skills/product/positioning-map/SKILL.md | 135 ++++++++ .../skills/product/prd-writer/SKILL.md | 135 ++++++++ .../skills/product/pricing-model/SKILL.md | 135 ++++++++ .../skills/product/product-brief/SKILL.md | 135 ++++++++ .../product/product-council-deck/SKILL.md | 135 ++++++++ .../product/product-documentation/SKILL.md | 135 ++++++++ .../product/product-health-check/SKILL.md | 135 ++++++++ .../product/product-launch-brief/SKILL.md | 135 ++++++++ .../product-metrics-framework/SKILL.md | 135 ++++++++ .../product/product-onboarding-flow/SKILL.md | 135 ++++++++ .../skills/product/product-one-pager/SKILL.md | 135 ++++++++ .../product/product-principles/SKILL.md | 135 ++++++++ .../product/product-retrospective/SKILL.md | 135 ++++++++ .../skills/product/product-review/SKILL.md | 135 ++++++++ .../skills/product/product-roadmap/SKILL.md | 135 ++++++++ .../skills/product/product-strategy/SKILL.md | 135 ++++++++ .../skills/product/product-vision/SKILL.md | 135 ++++++++ .../product/release-notes-writer/SKILL.md | 135 ++++++++ .../skills/product/release-planning/SKILL.md | 135 ++++++++ .../skills/product/rice-scoring/SKILL.md | 135 ++++++++ .../product/stakeholder-update/SKILL.md | 135 ++++++++ .../technical-debt-prioritization/SKILL.md | 135 ++++++++ .../product/technology-roadmap/SKILL.md | 135 ++++++++ .../product/trial-optimization/SKILL.md | 135 ++++++++ .../product/usability-test-plan/SKILL.md | 135 ++++++++ .../product/user-interview-guide/SKILL.md | 135 ++++++++ .../skills/product/user-journey-map/SKILL.md | 135 ++++++++ .../product/user-research-plan/SKILL.md | 135 ++++++++ .../skills/product/user-story/SKILL.md | 135 ++++++++ .../skills/productivity/annual-goals/SKILL.md | 133 ++++++++ .../skills/productivity/bio-writer/SKILL.md | 133 ++++++++ .../skills/productivity/book-summary/SKILL.md | 133 ++++++++ .../productivity/boundary-setting/SKILL.md | 133 ++++++++ .../productivity/burnout-prevention/SKILL.md | 133 ++++++++ .../productivity/career-development/SKILL.md | 133 ++++++++ .../productivity/career-pivot-plan/SKILL.md | 133 ++++++++ .../consulting-rate-calculator/SKILL.md | 133 ++++++++ .../skills/productivity/cover-letter/SKILL.md | 133 ++++++++ .../productivity/daily-planning/SKILL.md | 133 ++++++++ .../productivity/decision-matrix/SKILL.md | 133 ++++++++ .../productivity/deep-work-blocks/SKILL.md | 133 ++++++++ .../productivity/delegation-plan/SKILL.md | 133 ++++++++ .../productivity/eisenhower-matrix/SKILL.md | 133 ++++++++ .../productivity/email-management/SKILL.md | 133 ++++++++ .../email-template-library/SKILL.md | 133 ++++++++ .../productivity/energy-management/SKILL.md | 133 ++++++++ .../productivity/follow-up-system/SKILL.md | 133 ++++++++ .../productivity/freelance-proposal/SKILL.md | 133 ++++++++ .../productivity/goal-setting-okr/SKILL.md | 133 ++++++++ .../productivity/gratitude-practice/SKILL.md | 133 ++++++++ .../productivity/habit-stack-design/SKILL.md | 133 ++++++++ .../productivity/habit-tracker/SKILL.md | 133 ++++++++ .../productivity/inbox-zero-plan/SKILL.md | 133 ++++++++ .../productivity/journal-prompts/SKILL.md | 133 ++++++++ .../productivity/learning-plan/SKILL.md | 133 ++++++++ .../linkedin-profile-rewrite/SKILL.md | 133 ++++++++ .../linkedin-recommendation/SKILL.md | 133 ++++++++ .../meeting-agenda-personal/SKILL.md | 133 ++++++++ .../meeting-notes-summary/SKILL.md | 133 ++++++++ .../productivity/meeting-optimizer/SKILL.md | 133 ++++++++ .../skills/productivity/mit-method/SKILL.md | 133 ++++++++ .../productivity/networking-strategy/SKILL.md | 133 ++++++++ .../outsourcing-evaluation/SKILL.md | 133 ++++++++ .../peak-performance-schedule/SKILL.md | 133 ++++++++ .../personal-brand-audit/SKILL.md | 133 ++++++++ .../presentation-outline/SKILL.md | 133 ++++++++ .../productivity/priority-matrix/SKILL.md | 133 ++++++++ .../productivity/project-breakdown/SKILL.md | 133 ++++++++ .../productivity/pros-cons-analysis/SKILL.md | 133 ++++++++ .../public-speaking-prep/SKILL.md | 133 ++++++++ .../productivity/quarterly-goals/SKILL.md | 133 ++++++++ .../reflection-framework/SKILL.md | 133 ++++++++ .../relationship-management/SKILL.md | 133 ++++++++ .../productivity/resume-writer/SKILL.md | 133 ++++++++ .../productivity/routine-optimizer/SKILL.md | 133 ++++++++ .../productivity/salary-negotiation/SKILL.md | 133 ++++++++ .../productivity/side-project-plan/SKILL.md | 133 ++++++++ .../skill-acquisition-plan/SKILL.md | 133 ++++++++ .../storytelling-framework/SKILL.md | 133 ++++++++ .../productivity/task-decomposition/SKILL.md | 133 ++++++++ .../productivity/time-blocking/SKILL.md | 133 ++++++++ .../virtual-assistant-brief/SKILL.md | 133 ++++++++ .../productivity/weekly-review/SKILL.md | 133 ++++++++ .../productivity/weighted-scoring/SKILL.md | 133 ++++++++ .../work-breakdown-structure/SKILL.md | 133 ++++++++ .../productivity/work-life-audit/SKILL.md | 133 ++++++++ .../real-estate/1031-exchange-guide/SKILL.md | 133 ++++++++ .../real-estate/airbnb-analysis/SKILL.md | 133 ++++++++ .../real-estate/asset-allocation-re/SKILL.md | 133 ++++++++ .../real-estate/buyer-consultation/SKILL.md | 133 ++++++++ .../buyer-needs-assessment/SKILL.md | 133 ++++++++ .../real-estate/cap-rate-analysis/SKILL.md | 133 ++++++++ .../real-estate/cash-on-cash-return/SKILL.md | 133 ++++++++ .../commercial-property-analysis/SKILL.md | 133 ++++++++ .../comparative-market-analysis/SKILL.md | 133 ++++++++ .../real-estate/construction-budget/SKILL.md | 133 ++++++++ .../counter-offer-strategy/SKILL.md | 133 ++++++++ .../depreciation-analysis/SKILL.md | 133 ++++++++ .../development-feasibility/SKILL.md | 133 ++++++++ .../real-estate/exit-strategy-re/SKILL.md | 133 ++++++++ .../real-estate/farming-strategy/SKILL.md | 133 ++++++++ .../real-estate/investment-analysis/SKILL.md | 133 ++++++++ .../real-estate/just-sold-post/SKILL.md | 133 ++++++++ .../lease-agreement-checklist/SKILL.md | 133 ++++++++ .../real-estate/listing-description/SKILL.md | 133 ++++++++ .../listing-photography-brief/SKILL.md | 133 ++++++++ .../real-estate/listing-presentation/SKILL.md | 133 ++++++++ .../real-estate/maintenance-schedule/SKILL.md | 133 ++++++++ .../real-estate/market-analysis/SKILL.md | 133 ++++++++ .../market-update-newsletter/SKILL.md | 133 ++++++++ .../real-estate/negotiation-script/SKILL.md | 133 ++++++++ .../neighborhood-analysis/SKILL.md | 133 ++++++++ .../offer-letter-real-estate/SKILL.md | 133 ++++++++ .../office-lease-analysis/SKILL.md | 133 ++++++++ .../real-estate/open-house-plan/SKILL.md | 133 ++++++++ .../real-estate/portfolio-review/SKILL.md | 133 ++++++++ .../real-estate/project-timeline-re/SKILL.md | 133 ++++++++ .../real-estate/property-inspection/SKILL.md | 133 ++++++++ .../real-estate/property-listing/SKILL.md | 133 ++++++++ .../property-management-sop/SKILL.md | 133 ++++++++ .../real-estate-marketing-plan/SKILL.md | 133 ++++++++ .../real-estate/referral-program-re/SKILL.md | 133 ++++++++ .../rental-property-analysis/SKILL.md | 133 ++++++++ .../retail-space-evaluation/SKILL.md | 133 ++++++++ .../real-estate/seller-consultation/SKILL.md | 133 ++++++++ .../real-estate/showing-feedback/SKILL.md | 133 ++++++++ .../real-estate/sphere-of-influence/SKILL.md | 133 ++++++++ .../real-estate/tax-strategy-re/SKILL.md | 133 ++++++++ .../real-estate/tenant-screening/SKILL.md | 133 ++++++++ .../vacation-rental-strategy/SKILL.md | 133 ++++++++ .../real-estate/vendor-management-re/SKILL.md | 133 ++++++++ .../skills/sales/account-plan/SKILL.md | 134 ++++++++ .../skills/sales/affiliate-program/SKILL.md | 134 ++++++++ .../sales/boardroom-presentation/SKILL.md | 134 ++++++++ .../skills/sales/breakup-email/SKILL.md | 134 ++++++++ .../skills/sales/business-case/SKILL.md | 134 ++++++++ .../skills/sales/buyer-persona-sales/SKILL.md | 134 ++++++++ .../sales/cadence-optimization/SKILL.md | 134 ++++++++ .../skills/sales/case-study-sales/SKILL.md | 134 ++++++++ .../sales/channel-partner-strategy/SKILL.md | 134 ++++++++ .../skills/sales/churn-prevention/SKILL.md | 134 ++++++++ .../skills/sales/cold-call-script/SKILL.md | 134 ++++++++ .../.claude/skills/sales/cold-email/SKILL.md | 134 ++++++++ .../sales/cold-linkedin-message/SKILL.md | 134 ++++++++ .../sales/commission-structure/SKILL.md | 134 ++++++++ .../sales/competitor-battlecard/SKILL.md | 134 ++++++++ .../skills/sales/crm-setup-guide/SKILL.md | 134 ++++++++ .../skills/sales/cross-sell-playbook/SKILL.md | 134 ++++++++ .../skills/sales/deal-qualification/SKILL.md | 134 ++++++++ .../skills/sales/deal-scoring/SKILL.md | 134 ++++++++ .../.claude/skills/sales/demo-script/SKILL.md | 134 ++++++++ .../sales/discovery-call-guide/SKILL.md | 134 ++++++++ .../sales/executive-sponsor-plan/SKILL.md | 134 ++++++++ .../sales/expansion-revenue-plan/SKILL.md | 134 ++++++++ .../skills/sales/follow-up-email/SKILL.md | 134 ++++++++ .../skills/sales/forecast-model/SKILL.md | 134 ++++++++ .../sales/ideal-customer-profile/SKILL.md | 134 ++++++++ .../skills/sales/incentive-plan/SKILL.md | 134 ++++++++ .../skills/sales/lead-scoring-model/SKILL.md | 134 ++++++++ .../skills/sales/objection-handling/SKILL.md | 134 ++++++++ .../sales/onboarding-sales-rep/SKILL.md | 134 ++++++++ .../.claude/skills/sales/one-pager/SKILL.md | 134 ++++++++ .../skills/sales/pipeline-review/SKILL.md | 134 ++++++++ .../sales/pipeline-stage-definitions/SKILL.md | 134 ++++++++ .../skills/sales/pricing-negotiation/SKILL.md | 134 ++++++++ .../sales/procurement-response/SKILL.md | 134 ++++++++ .../skills/sales/proposal-writer/SKILL.md | 134 ++++++++ .../sales/quarterly-business-review/SKILL.md | 134 ++++++++ .../skills/sales/quota-planning/SKILL.md | 134 ++++++++ .../skills/sales/re-engagement-email/SKILL.md | 134 ++++++++ .../skills/sales/referral-ask/SKILL.md | 134 ++++++++ .../skills/sales/renewal-strategy/SKILL.md | 134 ++++++++ .../skills/sales/reseller-program/SKILL.md | 134 ++++++++ .../skills/sales/rfp-response-sales/SKILL.md | 134 ++++++++ .../skills/sales/roi-calculator/SKILL.md | 134 ++++++++ .../skills/sales/role-play-scenario/SKILL.md | 134 ++++++++ .../skills/sales/sales-automation/SKILL.md | 134 ++++++++ .../skills/sales/sales-contract/SKILL.md | 134 ++++++++ .../skills/sales/sales-dashboard/SKILL.md | 134 ++++++++ .../sales/sales-enablement-content/SKILL.md | 134 ++++++++ .../skills/sales/sales-kpi-tracker/SKILL.md | 134 ++++++++ .../skills/sales/sales-meeting-prep/SKILL.md | 134 ++++++++ .../.claude/skills/sales/sales-pitch/SKILL.md | 134 ++++++++ .../skills/sales/sales-playbook/SKILL.md | 134 ++++++++ .../sales/sales-process-design/SKILL.md | 134 ++++++++ .../skills/sales/sales-strategy/SKILL.md | 134 ++++++++ .../skills/sales/sales-training-plan/SKILL.md | 134 ++++++++ .../.claude/skills/sales/sell-sheet/SKILL.md | 134 ++++++++ .../skills/sales/sequence-design/SKILL.md | 134 ++++++++ .../skills/sales/spiff-program/SKILL.md | 134 ++++++++ .../skills/sales/statement-of-work/SKILL.md | 134 ++++++++ .../sales/strategic-account-review/SKILL.md | 134 ++++++++ .../skills/sales/target-account-list/SKILL.md | 134 ++++++++ .../skills/sales/territory-planning/SKILL.md | 134 ++++++++ .../skills/sales/upsell-strategy/SKILL.md | 134 ++++++++ .../sales/vendor-questionnaire/SKILL.md | 134 ++++++++ .../skills/sales/win-loss-analysis/SKILL.md | 134 ++++++++ .../seo/app-store-optimization/SKILL.md | 132 ++++++++ .../skills/seo/backlink-audit/SKILL.md | 132 ++++++++ .../skills/seo/broken-link-building/SKILL.md | 132 ++++++++ .../seo/canonical-tag-strategy/SKILL.md | 132 ++++++++ .../seo/category-page-optimization/SKILL.md | 132 ++++++++ .../seo/competitor-seo-analysis/SKILL.md | 132 ++++++++ .../seo/content-decay-analysis/SKILL.md | 132 ++++++++ .../skills/seo/content-refresh-plan/SKILL.md | 132 ++++++++ .../skills/seo/content-seo-brief/SKILL.md | 132 ++++++++ .../seo/conversion-tracking-setup/SKILL.md | 132 ++++++++ .../skills/seo/core-web-vitals-fix/SKILL.md | 132 ++++++++ .../seo/crawl-budget-optimization/SKILL.md | 132 ++++++++ .../skills/seo/digital-pr-plan/SKILL.md | 132 ++++++++ .../.claude/skills/seo/ecommerce-seo/SKILL.md | 132 ++++++++ .../featured-snippet-optimization/SKILL.md | 132 ++++++++ .../seo/google-analytics-setup/SKILL.md | 132 ++++++++ .../seo/google-business-profile/SKILL.md | 132 ++++++++ .../seo/google-search-console-audit/SKILL.md | 132 ++++++++ .../skills/seo/guest-post-outreach/SKILL.md | 132 ++++++++ .../.claude/skills/seo/haro-response/SKILL.md | 132 ++++++++ .../seo/header-tag-optimization/SKILL.md | 132 ++++++++ .../skills/seo/hreflang-setup/SKILL.md | 132 ++++++++ .../seo/image-alt-text-optimization/SKILL.md | 132 ++++++++ .../seo/internal-linking-strategy/SKILL.md | 132 ++++++++ .../skills/seo/international-seo/SKILL.md | 132 ++++++++ .../skills/seo/keyword-clustering/SKILL.md | 132 ++++++++ .../skills/seo/keyword-gap-analysis/SKILL.md | 132 ++++++++ .../skills/seo/keyword-research/SKILL.md | 132 ++++++++ .../seo/link-building-strategy/SKILL.md | 132 ++++++++ .../seo/local-citation-building/SKILL.md | 132 ++++++++ .../seo/local-keyword-strategy/SKILL.md | 132 ++++++++ .../skills/seo/local-link-building/SKILL.md | 132 ++++++++ .../skills/seo/local-seo-audit/SKILL.md | 132 ++++++++ .../seo/long-tail-keyword-finder/SKILL.md | 132 ++++++++ .../meta-description-optimization/SKILL.md | 132 ++++++++ .../seo/meta-title-optimization/SKILL.md | 132 ++++++++ .../seo/multilingual-seo-strategy/SKILL.md | 132 ++++++++ .../skills/seo/on-page-seo-audit/SKILL.md | 132 ++++++++ .../.claude/skills/seo/podcast-seo/SKILL.md | 132 ++++++++ .../skills/seo/product-page-seo/SKILL.md | 132 ++++++++ .../seo/question-keyword-research/SKILL.md | 132 ++++++++ .../.claude/skills/seo/redirect-map/SKILL.md | 132 ++++++++ .../seo/review-generation-plan/SKILL.md | 132 ++++++++ .../seo/robots-txt-optimization/SKILL.md | 132 ++++++++ .../seo/schema-markup-generator/SKILL.md | 132 ++++++++ .../seo/search-intent-analysis/SKILL.md | 132 ++++++++ .../skills/seo/seo-content-audit/SKILL.md | 132 ++++++++ .../skills/seo/seo-content-outline/SKILL.md | 132 ++++++++ .../.claude/skills/seo/seo-forecast/SKILL.md | 132 ++++++++ .../seo/seo-reporting-dashboard/SKILL.md | 132 ++++++++ .../.claude/skills/seo/seo-roadmap/SKILL.md | 132 ++++++++ .../.claude/skills/seo/serp-analysis/SKILL.md | 132 ++++++++ .../skills/seo/site-speed-analysis/SKILL.md | 132 ++++++++ .../skills/seo/technical-seo-audit/SKILL.md | 132 ++++++++ .../skills/seo/topical-authority-map/SKILL.md | 132 ++++++++ .../seo/xml-sitemap-optimization/SKILL.md | 132 ++++++++ .../.claude/skills/seo/youtube-seo/SKILL.md | 132 ++++++++ .../skills/social-media/bluesky-post/SKILL.md | 133 ++++++++ .../brand-ambassador-program/SKILL.md | 133 ++++++++ .../community-guidelines/SKILL.md | 133 ++++++++ .../social-media/creator-partnership/SKILL.md | 133 ++++++++ .../cross-platform-strategy/SKILL.md | 133 ++++++++ .../employee-advocacy-program/SKILL.md | 133 ++++++++ .../engagement-rate-analysis/SKILL.md | 133 ++++++++ .../executive-social-strategy/SKILL.md | 133 ++++++++ .../facebook-event-promotion/SKILL.md | 133 ++++++++ .../facebook-group-strategy/SKILL.md | 133 ++++++++ .../social-media/facebook-post/SKILL.md | 133 ++++++++ .../follower-growth-strategy/SKILL.md | 133 ++++++++ .../influencer-collaboration-brief/SKILL.md | 133 ++++++++ .../instagram-bio-optimization/SKILL.md | 133 ++++++++ .../social-media/instagram-carousel/SKILL.md | 133 ++++++++ .../instagram-hashtag-strategy/SKILL.md | 133 ++++++++ .../social-media/instagram-post/SKILL.md | 133 ++++++++ .../instagram-reel-script/SKILL.md | 133 ++++++++ .../instagram-story-sequence/SKILL.md | 133 ++++++++ .../social-media/linkedin-article/SKILL.md | 133 ++++++++ .../social-media/linkedin-carousel/SKILL.md | 133 ++++++++ .../linkedin-company-page/SKILL.md | 133 ++++++++ .../social-media/linkedin-outreach/SKILL.md | 133 ++++++++ .../social-media/linkedin-post/SKILL.md | 133 ++++++++ .../linkedin-profile-optimization/SKILL.md | 133 ++++++++ .../social-media/mastodon-post/SKILL.md | 133 ++++++++ .../negative-comment-response/SKILL.md | 133 ++++++++ .../pinterest-board-strategy/SKILL.md | 133 ++++++++ .../social-media/pinterest-pin/SKILL.md | 133 ++++++++ .../social-media/pinterest-seo/SKILL.md | 133 ++++++++ .../platform-migration-plan/SKILL.md | 133 ++++++++ .../social-media/reddit-ama-plan/SKILL.md | 133 ++++++++ .../reddit-community-strategy/SKILL.md | 133 ++++++++ .../skills/social-media/reddit-post/SKILL.md | 133 ++++++++ .../social-media/review-response/SKILL.md | 133 ++++++++ .../social-media/sentiment-analysis/SKILL.md | 133 ++++++++ .../skills/social-media/social-audit/SKILL.md | 133 ++++++++ .../social-content-calendar/SKILL.md | 133 ++++++++ .../social-media/social-contest/SKILL.md | 133 ++++++++ .../social-listening-report/SKILL.md | 133 ++++++++ .../social-media-bio-generator/SKILL.md | 133 ++++++++ .../social-media-crisis-response/SKILL.md | 133 ++++++++ .../social-media/social-media-policy/SKILL.md | 133 ++++++++ .../social-media-response/SKILL.md | 133 ++++++++ .../social-media/social-selling/SKILL.md | 133 ++++++++ .../social-media/social-strategy/SKILL.md | 133 ++++++++ .../skills/social-media/threads-post/SKILL.md | 133 ++++++++ .../tiktok-content-strategy/SKILL.md | 133 ++++++++ .../tiktok-duet-strategy/SKILL.md | 133 ++++++++ .../tiktok-hook-generator/SKILL.md | 133 ++++++++ .../social-media/tiktok-script/SKILL.md | 133 ++++++++ .../social-media/tiktok-series-plan/SKILL.md | 133 ++++++++ .../tiktok-trend-analysis/SKILL.md | 133 ++++++++ .../skills/social-media/trend-report/SKILL.md | 133 ++++++++ .../twitter-engagement-strategy/SKILL.md | 133 ++++++++ .../twitter-growth-strategy/SKILL.md | 133 ++++++++ .../skills/social-media/twitter-post/SKILL.md | 133 ++++++++ .../twitter-profile-optimization/SKILL.md | 133 ++++++++ .../social-media/twitter-spaces-plan/SKILL.md | 133 ++++++++ .../social-media/twitter-thread/SKILL.md | 133 ++++++++ .../skills/social-media/ugc-strategy/SKILL.md | 133 ++++++++ .../user-generated-content-brief/SKILL.md | 133 ++++++++ .../viral-content-formula/SKILL.md | 133 ++++++++ .../youtube-channel-strategy/SKILL.md | 133 ++++++++ .../youtube-description-seo/SKILL.md | 133 ++++++++ .../youtube-playlist-strategy/SKILL.md | 133 ++++++++ .../youtube-shorts-script/SKILL.md | 133 ++++++++ .../youtube-title-thumbnail/SKILL.md | 133 ++++++++ .../youtube-video-outline/SKILL.md | 133 ++++++++ .../startup/accelerator-application/SKILL.md | 132 ++++++++ .../skills/startup/acquisition-prep/SKILL.md | 132 ++++++++ .../startup/advisory-board-setup/SKILL.md | 132 ++++++++ .../skills/startup/board-deck/SKILL.md | 132 ++++++++ .../skills/startup/bootstrap-plan/SKILL.md | 132 ++++++++ .../startup/brand-name-generator/SKILL.md | 132 ++++++++ .../startup/build-measure-learn/SKILL.md | 132 ++++++++ .../startup/business-model-canvas/SKILL.md | 132 ++++++++ .../skills/startup/business-plan/SKILL.md | 132 ++++++++ .../startup/cap-table-management/SKILL.md | 132 ++++++++ .../startup/co-founder-agreement/SKILL.md | 132 ++++++++ .../startup/competitive-landscape/SKILL.md | 132 ++++++++ .../skills/startup/culture-code/SKILL.md | 132 ++++++++ .../startup/customer-discovery/SKILL.md | 132 ++++++++ .../skills/startup/data-room-setup/SKILL.md | 132 ++++++++ .../startup/defensibility-assessment/SKILL.md | 132 ++++++++ .../startup/distribution-strategy/SKILL.md | 132 ++++++++ .../startup/domain-name-strategy/SKILL.md | 132 ++++++++ .../startup/due-diligence-prep/SKILL.md | 132 ++++++++ .../skills/startup/equity-split/SKILL.md | 132 ++++++++ .../skills/startup/exit-strategy/SKILL.md | 132 ++++++++ .../startup/fundraising-strategy/SKILL.md | 132 ++++++++ .../startup/growth-experiment-design/SKILL.md | 132 ++++++++ .../skills/startup/growth-metrics/SKILL.md | 132 ++++++++ .../skills/startup/growth-strategy/SKILL.md | 132 ++++++++ .../skills/startup/hiring-first-ten/SKILL.md | 132 ++++++++ .../startup/incorporation-guide/SKILL.md | 132 ++++++++ .../skills/startup/investor-outreach/SKILL.md | 132 ++++++++ .../startup/investor-pitch-script/SKILL.md | 132 ++++++++ .../startup/investor-target-list/SKILL.md | 132 ++++++++ .../startup/investor-update-template/SKILL.md | 132 ++++++++ .../skills/startup/ipo-readiness/SKILL.md | 132 ++++++++ .../skills/startup/kill-criteria/SKILL.md | 132 ++++++++ .../skills/startup/lean-canvas/SKILL.md | 132 ++++++++ .../skills/startup/market-validation/SKILL.md | 132 ++++++++ .../startup/marketplace-launch/SKILL.md | 132 ++++++++ .../skills/startup/mentor-outreach/SKILL.md | 132 ++++++++ .../skills/startup/moat-analysis/SKILL.md | 132 ++++++++ .../startup/monetization-strategy/SKILL.md | 132 ++++++++ .../skills/startup/mvp-definition/SKILL.md | 132 ++++++++ .../skills/startup/mvp-feature-list/SKILL.md | 132 ++++++++ .../skills/startup/one-page-memo/SKILL.md | 132 ++++++++ .../partnership-strategy-startup/SKILL.md | 132 ++++++++ .../skills/startup/pitch-deck/SKILL.md | 132 ++++++++ .../skills/startup/pivot-assessment/SKILL.md | 132 ++++++++ .../skills/startup/pivot-plan/SKILL.md | 132 ++++++++ .../skills/startup/pmf-survey/SKILL.md | 132 ++++++++ .../startup/pricing-experiment/SKILL.md | 132 ++++++++ .../startup/problem-validation/SKILL.md | 132 ++++++++ .../startup/product-market-fit/SKILL.md | 132 ++++++++ .../startup/remote-startup-playbook/SKILL.md | 132 ++++++++ .../retention-analysis-startup/SKILL.md | 132 ++++++++ .../startup/revenue-model-design/SKILL.md | 132 ++++++++ .../startup/side-project-validation/SKILL.md | 132 ++++++++ .../startup/solopreneur-playbook/SKILL.md | 132 ++++++++ .../startup/startup-legal-checklist/SKILL.md | 132 ++++++++ .../startup-metrics-dashboard/SKILL.md | 132 ++++++++ .../skills/startup/team-building/SKILL.md | 132 ++++++++ .../startup/term-sheet-negotiation/SKILL.md | 132 ++++++++ .../skills/startup/trademark-search/SKILL.md | 132 ++++++++ .../travel/accommodation-comparison/SKILL.md | 132 ++++++++ .../skills/travel/activity-planner/SKILL.md | 132 ++++++++ .../travel/adventure-travel-plan/SKILL.md | 132 ++++++++ .../skills/travel/airbnb-listing/SKILL.md | 132 ++++++++ .../skills/travel/bleisure-guide/SKILL.md | 132 ++++++++ .../travel/budget-travel-guide/SKILL.md | 132 ++++++++ .../skills/travel/catering-menu/SKILL.md | 132 ++++++++ .../travel/conference-planning/SKILL.md | 132 ++++++++ .../travel/corporate-travel-policy/SKILL.md | 132 ++++++++ .../skills/travel/cost-comparison/SKILL.md | 132 ++++++++ .../crisis-management-hospitality/SKILL.md | 132 ++++++++ .../travel/day-by-day-itinerary/SKILL.md | 132 ++++++++ .../skills/travel/destination-guide/SKILL.md | 132 ++++++++ .../travel/destination-marketing/SKILL.md | 132 ++++++++ .../skills/travel/dining-guide/SKILL.md | 132 ++++++++ .../dynamic-pricing-hospitality/SKILL.md | 132 ++++++++ .../skills/travel/eco-tourism-guide/SKILL.md | 132 ++++++++ .../travel/emergency-procedure/SKILL.md | 132 ++++++++ .../travel/event-planning-venue/SKILL.md | 132 ++++++++ .../skills/travel/excursion-brief/SKILL.md | 132 ++++++++ .../travel/family-vacation-planner/SKILL.md | 132 ++++++++ .../skills/travel/food-tour-plan/SKILL.md | 132 ++++++++ .../travel/front-desk-procedure/SKILL.md | 132 ++++++++ .../skills/travel/group-travel-plan/SKILL.md | 132 ++++++++ .../travel/guest-experience-audit/SKILL.md | 132 ++++++++ .../travel/guest-feedback-analysis/SKILL.md | 132 ++++++++ .../skills/travel/guest-persona/SKILL.md | 132 ++++++++ .../travel/health-safety-protocol/SKILL.md | 132 ++++++++ .../skills/travel/honeymoon-planner/SKILL.md | 132 ++++++++ .../travel/hotel-operations-sop/SKILL.md | 132 ++++++++ .../skills/travel/hotel-review/SKILL.md | 132 ++++++++ .../travel/housekeeping-checklist/SKILL.md | 132 ++++++++ .../skills/travel/itinerary-planner/SKILL.md | 132 ++++++++ .../loyalty-program-hospitality/SKILL.md | 132 ++++++++ .../travel/luxury-travel-concierge/SKILL.md | 132 ++++++++ .../travel/multi-city-itinerary/SKILL.md | 132 ++++++++ .../travel/occupancy-optimization/SKILL.md | 132 ++++++++ .../skills/travel/packing-checklist/SKILL.md | 132 ++++++++ .../skills/travel/responsible-travel/SKILL.md | 132 ++++++++ .../travel/restaurant-recommendation/SKILL.md | 132 ++++++++ .../skills/travel/revenue-management/SKILL.md | 132 ++++++++ .../skills/travel/seasonal-promotion/SKILL.md | 132 ++++++++ .../skills/travel/service-recovery/SKILL.md | 132 ++++++++ .../skills/travel/solo-travel-guide/SKILL.md | 132 ++++++++ .../sustainability-plan-travel/SKILL.md | 132 ++++++++ .../skills/travel/tour-guide-script/SKILL.md | 132 ++++++++ .../skills/travel/tourism-marketing/SKILL.md | 132 ++++++++ .../skills/travel/travel-blog-post/SKILL.md | 132 ++++++++ .../travel/travel-budget-calculator/SKILL.md | 132 ++++++++ .../travel/travel-document-checklist/SKILL.md | 132 ++++++++ .../travel/travel-photography-guide/SKILL.md | 132 ++++++++ .../travel/travel-savings-plan/SKILL.md | 132 ++++++++ .../upsell-strategy-hospitality/SKILL.md | 132 ++++++++ .../skills/travel/visa-requirements/SKILL.md | 132 ++++++++ clowdex-download/.claude/.mcp.json | 14 + clowdex-download/.claude/CLAUDE.local.md | 18 + clowdex-download/.claude/CLAUDE.md | 279 ++++++++++++++++ clowdex-download/.claude/SETUP.md | 149 +++++++++ clowdex-download/.claude/Scratchpad.md | 5 + clowdex-download/.claude/Task Board.md | 13 + docker-compose.yml | 47 +++ docs/schema.md | 101 ++++++ frontend/package.json | 0 frontend/vite.config.ts | 0 1867 files changed, 243740 insertions(+) create mode 100644 .claude/knowledge-base.md create mode 100644 .claude/memory.md create mode 100644 .env.example create mode 100644 .gitignore create mode 100644 .nextcloudignore create mode 100644 README.md create mode 100644 Task Board.md create mode 100644 backend/__init__.py create mode 100644 backend/auth.py create mode 100644 backend/database.py create mode 100644 backend/main.py create mode 100644 backend/models.py create mode 100644 backend/requirements.txt create mode 100644 backend/routers/__init__.py create mode 100644 backend/routers/emails.py create mode 100644 backend/routers/invoices.py create mode 100644 backend/schemas.py create mode 100644 clowdex-download/.claude/.claude/agent-memory/ledger/MEMORY.md create mode 100644 clowdex-download/.claude/.claude/agent-memory/scout/MEMORY.md create mode 100644 clowdex-download/.claude/.claude/agent-memory/sentinel/MEMORY.md create mode 100644 clowdex-download/.claude/.claude/agents/compass.md create mode 100644 clowdex-download/.claude/.claude/agents/decoder.md create mode 100644 clowdex-download/.claude/.claude/agents/historian.md create mode 100644 clowdex-download/.claude/.claude/agents/ledger.md create mode 100644 clowdex-download/.claude/.claude/agents/mirror.md create mode 100644 clowdex-download/.claude/.claude/agents/pathfinder.md create mode 100644 clowdex-download/.claude/.claude/agents/scout.md create mode 100644 clowdex-download/.claude/.claude/agents/scribe.md create mode 100644 clowdex-download/.claude/.claude/agents/sentinel.md create mode 100644 clowdex-download/.claude/.claude/command-index.md create mode 100644 clowdex-download/.claude/.claude/commands/audit.md create mode 100644 clowdex-download/.claude/.claude/commands/brief.md create mode 100644 clowdex-download/.claude/.claude/commands/check-drift.md create mode 100644 clowdex-download/.claude/.claude/commands/create-playbook.md create mode 100644 clowdex-download/.claude/.claude/commands/end-day.md create mode 100644 clowdex-download/.claude/.claude/commands/flush.md create mode 100644 clowdex-download/.claude/.claude/commands/handoff.md create mode 100644 clowdex-download/.claude/.claude/commands/launch.md create mode 100644 clowdex-download/.claude/.claude/commands/market-scan.md create mode 100644 clowdex-download/.claude/.claude/commands/onboard.md create mode 100644 clowdex-download/.claude/.claude/commands/proposal.md create mode 100644 clowdex-download/.claude/.claude/commands/release.md create mode 100644 clowdex-download/.claude/.claude/commands/report.md create mode 100644 clowdex-download/.claude/.claude/commands/retro.md create mode 100644 clowdex-download/.claude/.claude/commands/review.md create mode 100644 clowdex-download/.claude/.claude/commands/standup.md create mode 100644 clowdex-download/.claude/.claude/commands/start.md create mode 100644 clowdex-download/.claude/.claude/commands/sync.md create mode 100644 clowdex-download/.claude/.claude/commands/system-audit.md create mode 100644 clowdex-download/.claude/.claude/commands/tech-debt.md create mode 100644 clowdex-download/.claude/.claude/commands/unstick.md create mode 100755 clowdex-download/.claude/.claude/hooks/backup-before-write.sh create mode 100755 clowdex-download/.claude/.claude/hooks/completeness-gate.sh create mode 100755 clowdex-download/.claude/.claude/hooks/guard-bash.sh create mode 100755 clowdex-download/.claude/.claude/hooks/log-changes.sh create mode 100755 clowdex-download/.claude/.claude/hooks/log-failures.sh create mode 100755 clowdex-download/.claude/.claude/hooks/log-stop-verdict.sh create mode 100755 clowdex-download/.claude/.claude/hooks/post-compact-resume.sh create mode 100755 clowdex-download/.claude/.claude/hooks/pre-compact-handoff.sh create mode 100755 clowdex-download/.claude/.claude/hooks/session-reset.sh create mode 100644 clowdex-download/.claude/.claude/knowledge-base.md create mode 100644 clowdex-download/.claude/.claude/knowledge-nominations.md create mode 100644 clowdex-download/.claude/.claude/memory.md create mode 100644 clowdex-download/.claude/.claude/settings.json create mode 100644 clowdex-download/.claude/.claude/skills/INDEX.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/animal-welfare-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/breeding-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/carbon-footprint/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/conservation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/cost-per-acre/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/crop-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/csa-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/direct-to-consumer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/disaster-preparedness-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/equipment-maintenance-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/equipment-roi/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/farm-budget/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/farm-business-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/farm-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/farmers-market-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/feed-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/fertilizer-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/grant-application-agriculture/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/harvest-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/health-protocol-livestock/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/insurance-review-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/integrated-pest-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/irrigation-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/labor-management-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/land-acquisition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/lease-negotiation-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/livestock-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/organic-certification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/pasture-rotation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/pest-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/planting-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/post-harvest-handling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/profit-analysis-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/regenerative-practices/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/seasonal-hiring/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/soil-analysis-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/storage-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/subsidy-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/succession-planning-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/sustainability-report-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/technology-adoption/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/value-added-product/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/weather-contingency/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/wholesale-channel/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/agriculture/worker-safety-farm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/agent-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-adoption-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-agent-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-assistant-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-bias-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-change-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-code-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-compliance-documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-content-pipeline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-content-policy-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-cost-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-customer-service/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-data-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-debugging-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-editing-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-email-drafting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-ethics-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-financial-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-healthcare-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-image-prompt/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-image-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-meeting-notes/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-pair-programming/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-readiness-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-research-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-summarization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-training-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-transcription-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-translation-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-use-case-identification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-ux-design-patterns/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-vendor-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-voice-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-workflow-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/ai-writing-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/algorithmic-impact-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/api-integration-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/automation-opportunity-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/automation-roi-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/chatbot-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/conversational-flow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/creative-ai-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/enterprise-ai-governance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/eu-ai-act-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/fine-tuning-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/intelligent-automation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/knowledge-base-ai/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/llm-application-architecture/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/llm-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/make-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/multi-agent-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/n8n-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/no-code-automation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/process-mining/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/prompt-engineering-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/prompt-evaluation-harness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/prompt-template-builder/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/prompt-testing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/rag-system-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/responsible-ai-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/rpa-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/synthetic-data-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/webhook-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ai-automation/zapier-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/apprenticeship-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/as-built-documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/bid-submission/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/budget-tracking-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/change-order/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/client-update-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/code-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/completion-certificate/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/cost-variance-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/critical-path/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/employee-certification-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/environmental-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/equipment-maintenance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/fleet-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/gantt-chart-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/incident-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/inspection-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/labor-estimate/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/maintenance-manual/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/marketing-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/material-takeoff/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/payment-application/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/permit-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/portfolio-showcase/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/progress-report-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/project-estimate/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/project-proposal-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/project-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/punch-list/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/quality-control-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/referral-strategy-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/safety-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/safety-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/scope-of-work-construction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/site-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/soil-report-summary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/subcontractor-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/subcontractor-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/tool-inventory/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/toolbox-talk/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/warranty-document/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/construction/zoning-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/100-day-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/benchmarking-study/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/board-presentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/build-vs-buy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/capability-building/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/change-readiness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/client-discovery-workshop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/client-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/core-competency-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/cost-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/culture-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/current-state-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/customer-experience-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/digital-transformation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/disruption-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/diversification-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/due-diligence-commercial/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/engagement-letter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/executive-presentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/expansion-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/gap-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/implementation-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/industry-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/innovation-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/integration-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/journey-mapping/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/knowledge-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/lean-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/market-entry-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/market-landscape/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/maturity-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/operating-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/organizational-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/pestel-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/porters-five-forces/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/post-merger-integration/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/process-improvement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/recommendation-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/red-team-exercise/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/scenario-planning-consulting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/scope-of-work/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/service-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/shared-services/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/six-sigma-project/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/stakeholder-interview-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/strategy-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/swot-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/talent-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/technology-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/transformation-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/trend-analysis-consulting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/value-chain-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/vendor-selection/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/consulting/war-gaming/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/about-page-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-facebook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-google/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-linkedin/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-tiktok/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-twitter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ad-copy-youtube/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/annual-report-narrative/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/api-documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/blog-content-calendar/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/blog-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/blog-series-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/brand-story/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/business-proposal-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/byline-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/case-study/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/changelog/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/checkout-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/company-update/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/comparison-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/content-atomization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/content-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/content-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/content-gap-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/content-repurposing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/cta-optimizer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/customer-story/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ebook-chapter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/ebook-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/elevator-pitch-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/email-body-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/email-sequence-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/email-subject-lines/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/empty-state-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/error-message-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/explainer-video-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/faq-page/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/feature-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/grant-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/headline-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/homepage-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/how-to-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/in-app-message-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/industry-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/investor-update/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/keynote-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/landing-page-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/listicle/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/manifesto-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/media-advisory/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/microcopy-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/mission-statement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/naming-brainstorm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/newsletter-issue/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/newsletter-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/newsletter-welcome-series/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/onboarding-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/opinion-piece/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/origin-story/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/pillar-page/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/podcast-episode-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/podcast-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/podcast-show-notes/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/presentation-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/press-release-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/pricing-page-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/product-description/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/product-page-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/push-notification-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/release-notes/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/rfp-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/slogan-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/sms-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/social-proof-page/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/speech-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/style-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/tagline-brainstorm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/technical-writing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/testimonial-request/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/thought-leadership-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/tone-of-voice-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/tutorial-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/user-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/value-proposition-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/video-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/vision-statement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/content/whitepaper/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/advocacy-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/ai-support-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/beta-tester-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/certification-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/champion-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/chatbot-conversation-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/chatbot-decision-tree/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/churn-prevention-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/churn-risk-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/community-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/cs-cadence-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/csat-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-advisory-board/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-communication-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-effort-score/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-feedback-loop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-health-score/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-journey-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-onboarding-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-success-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-training-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/customer-welcome-kit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/escalation-procedure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/expansion-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/experience-mapping/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/feature-announcement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/feedback-categorization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/forum-moderation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/friction-point-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/help-center-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/implementation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/knowledge-base-article-support/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/nps-survey-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/outage-communication/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/qbr-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/quality-assurance-support/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/renewal-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/response-time-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/self-service-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/sla-definition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/support-metrics-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/support-retrospective/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/support-team-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/support-ticket-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/tier-support-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/user-group-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/voice-of-customer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/customer-success/webinar-series/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/access-control-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/api-security-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/attack-surface-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/backup-validation-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/bcp/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/board-security-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/cloud-security-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/compliance-gap-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/data-breach-notification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/data-classification-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/detection-rule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/disaster-recovery-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/dpia/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/encryption-standard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/forensics-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/hipaa-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/iam-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/incident-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/incident-response-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/ir-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/iso27001-isms/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/network-security-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/nist-csf-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/pam-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/pci-dss-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/pentest-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/phishing-simulation-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/privacy-program-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/purple-team-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/red-team-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/risk-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/risk-register/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/runbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/sbom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/sdlc-security-gates/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/secure-code-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/secure-design-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/security-architecture-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/security-awareness-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/security-monitoring-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/security-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/soc-maturity-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/soc-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/soc2-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/social-engineering-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/tabletop-exercise/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/threat-intel-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/threat-landscape-briefing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/threat-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/vendor-risk-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/vuln-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/web-app-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/wireless-security-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/cybersecurity/zero-trust-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/ab-test-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/analytics-implementation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/attribution-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/benchmark-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/chart-selection-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/clustering-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/cohort-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/competitive-data-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/customer-segmentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/dashboard-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-access-control/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-analysis-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-catalog/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-cleaning-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-dictionary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-driven-recommendation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-governance-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-mart-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-privacy-impact/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-quality-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-storytelling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-validation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-visualization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/data-warehouse-schema/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/database-performance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/etl-pipeline-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/event-taxonomy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/executive-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/experiment-results/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/exploratory-data-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/forecasting-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/funnel-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/incrementality-test/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/industry-data-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/infographic-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/insight-presentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/kpi-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/marketing-mix-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/metadata-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/ml-experiment-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/model-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/monthly-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/nps-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/predictive-model-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/query-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/report-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/retention-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/rfm-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/sql-query-builder/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/statistical-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/statistical-significance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/survey-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/survey-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/time-series-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/tracking-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/trend-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/data/weekly-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/accessibility-design-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/animation-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/art-direction-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/brand-application-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/brand-asset-library/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/brand-guidelines-doc/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/brand-identity-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/campaign-creative-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/color-palette-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/component-library-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/creative-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/creative-campaign-concept/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/creative-review-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/data-visualization-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-critique-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-handoff/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-sprint/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-thinking-workshop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/design-tokens/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/email-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/icon-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/ideation-session/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/illustration-style-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/inclusive-design-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/infographic-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/information-architecture/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/interaction-design-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/landing-page-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/logo-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/mobile-design-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/mood-board/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/packaging-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/persona-ux/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/photo-direction-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/presentation-design-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/print-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/prototype-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/responsive-design-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/signage-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/social-media-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/storyboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/style-tile/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/tablet-design-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/typography-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/usability-test/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/user-flow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/user-interview-ux/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/ux-research-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/video-direction-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/visual-direction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/wcag-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/design/wireframe-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/accessibility-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/alerting-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/api-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/api-documentation-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/api-gateway-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/api-versioning-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/architecture-decision-record/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/architecture-overview/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/blue-green-deployment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/branching-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/caching-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/canary-deployment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/ci-cd-pipeline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/circuit-breaker-pattern/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/code-cleanup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/code-review-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/codebase-walkthrough/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/coding-standards/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/commit-message-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/contributing-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/cross-browser-testing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/data-model-documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/database-schema-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/dependency-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/deployment-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/dev-environment-parity/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/developer-onboarding/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/distributed-tracing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/docker-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/documentation-standard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/e2e-test-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/environment-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/error-handling-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/event-driven-architecture/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/feature-flag-implementation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/git-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/incident-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/infrastructure-as-code/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/integration-test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/kubernetes-deployment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/license-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/linting-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/load-test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/local-dev-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/logging-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/microservices-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/migration-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/monitoring-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/observability-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/on-call-runbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/open-source-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/optimization-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/package-publishing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/performance-profiling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/postmortem-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/pre-commit-hooks/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/pull-request-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/queue-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/readme-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/refactoring-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/release-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/responsive-design-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/retry-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/rollback-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/root-cause-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/security-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/security-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/semantic-versioning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/service-boundary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/supply-chain-security/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/system-design-doc/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/tech-debt-inventory/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/technical-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/test-coverage-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/testing-pyramid/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/unit-test-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/development/vulnerability-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/amazon-listing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/amazon-ppc-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/black-friday-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/bundle-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/cart-abandonment-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/category-taxonomy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/checkout-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/collection-page-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/conversion-rate-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/cross-border-ecommerce/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/customer-acquisition-cost/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/customer-lifetime-value/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/customer-review-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/customer-segmentation-ecom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/dead-stock-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/dropshipping-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/dynamic-pricing-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/ecommerce-analytics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/email-marketing-ecom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/etsy-listing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/flash-sale-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/fulfillment-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/inventory-forecasting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/landing-page-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/localization-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/loyalty-program-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/marketplace-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/multi-currency-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/personalization-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/pricing-strategy-ecom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-description-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-listing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-page-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-performance-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-photography-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-title-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/product-video-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/push-notification-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/recommendation-engine/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/returns-policy-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/review-response-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/sales-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/seasonal-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/shipping-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/shopify-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/sms-marketing-ecom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/social-proof-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/stock-level-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/subscription-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/supplier-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/unit-economics-ecom/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/vip-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/wholesale-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/ecommerce/woocommerce-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/assessment-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/badge-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/case-study-teaching/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/certification-program-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/coaching-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/cohort-based-course/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/competency-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/compliance-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/content-accessibility/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/corporate-training-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/course-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/course-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/course-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/credentialing-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/curriculum-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/customer-service-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/educational-content-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/exam-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/leadership-development/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/learning-analytics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/learning-objectives/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/learning-path/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/lesson-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/live-session-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/lms-content-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/management-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/mentorship-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/microlearning-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/module-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/office-hours-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/onboarding-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/online-course-launch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/peer-learning-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/quiz-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/role-play-scenario-edu/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/rubric-creator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/sales-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/scorm-module-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/simulation-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/skills-gap-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/soft-skills-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/student-feedback-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/student-onboarding/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/study-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/technical-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/training-needs-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/tutoring-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/universal-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/workshop-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/workshop-facilitator-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/education/workshop-materials/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/announcement-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/browse-abandonment-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/can-spam-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/cart-abandonment-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/cold-outreach-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/confirmation-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/deliverability-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/domain-reputation-fix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-ab-test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-analytics-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-automation-workflow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-benchmark-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-compliance-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-optimization-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-reporting-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-segmentation-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-subject-line-testing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/email-template-design-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/event-invitation-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/feature-launch-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/flash-sale-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/gdpr-email-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/html-email-spec/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/launch-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/lifecycle-email-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/list-cleaning-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/newsletter-editorial-calendar/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/newsletter-growth-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/newsletter-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/nurture-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/onboarding-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/partnership-outreach-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/password-reset-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/plain-text-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/post-event-follow-up/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/post-purchase-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/pr-outreach-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/product-update-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/promotional-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/re-engagement-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/referral-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/review-request-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/seasonal-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/subscriber-scoring/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/sunset-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/transactional-email-copy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/trigger-email-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/warm-up-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/webinar-reminder-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/welcome-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/email/win-back-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/adaptation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/battery-storage-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/carbon-footprint-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/carbon-offset-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/circular-economy-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/climate-risk-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/community-impact/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/conservation-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/energy-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/energy-management-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/energy-savings-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/energy-star-certification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/environmental-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/environmental-impact-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/esg-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/ev-fleet-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/ghg-inventory/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/green-building-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/green-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/green-vendor-criteria/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/greenwashing-check/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/iso-50001-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/leed-preparation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/materiality-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/net-zero-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/permit-tracking/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/ppa-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/recycling-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/renewable-energy-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/renewable-energy-certificate/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/resilience-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/science-based-targets/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/scope-3-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/social-license/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/solar-feasibility/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/stakeholder-engagement-esg/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/supplier-sustainability-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/sustainability-communication/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/sustainability-report-esg/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/sustainability-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/sustainable-procurement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/utility-bill-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/waste-management-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/water-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/energy/water-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/acquisition-due-diligence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/balance-sheet-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/board-financial-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/bonus-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/break-even-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/budget-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/budget-variance-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/cap-table/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/cash-flow-forecast/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/cash-flow-statement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/collections-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/compensation-benchmarking/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/competitive-pricing-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/compliance-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/cost-benefit-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/cost-reduction-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/dcf-valuation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/deduction-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/deferred-revenue-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/depreciation-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/expense-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/expense-report-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/financial-audit-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/financial-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/financial-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/financial-ratio-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/fundraising-financial-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/internal-controls/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/inventory-valuation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/investor-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/invoice-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/kpi-scorecard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/management-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/merger-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/monte-carlo-simulation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/mrr-arr-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/npv-irr-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/payback-period-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/payment-terms/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/price-sensitivity-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/pricing-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/procurement-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/profit-loss-statement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/quarterly-financial-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/quarterly-tax-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/revenue-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/revenue-recognition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/roi-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/runway-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/salary-band-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/scenario-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/sensitivity-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/subscription-cost-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/synergy-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/tax-planning-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/term-sheet-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/unit-economics-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/vendor-payment-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/working-capital-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/finance/zero-based-budget/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/app-programming/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/body-composition-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/bootcamp-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/breathwork-session/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/certification-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/class-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/cleaning-protocol/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/client-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/client-onboarding-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/client-retention-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/content-plan-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/continuing-education-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/corporate-wellness-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/equipment-maintenance-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-business-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-test/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/goal-setting-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/group-fitness-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/habit-change-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/injury-prevention/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/meal-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/meditation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/membership-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/nutrition-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/online-coaching-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/periodization-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/pricing-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/progress-tracking/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/referral-program-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/rehab-protocol-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/retreat-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/return-to-sport/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/social-media-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/specialization-track/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/stress-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/studio-operations/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/supplement-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/testimonial-collection/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/training-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/transformation-story/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/virtual-training-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/wellness-coaching-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/workout-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/workshop-fitness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/fitness-wellness/yoga-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/allergen-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/bar-training/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/brand-standards/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/catering-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/cocktail-menu/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/concept-development/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/cross-training-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/customer-feedback-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/delivery-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/event-menu-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/food-cost-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/food-safety-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/franchise-operations-manual/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/haccp-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/health-inspection-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/influencer-dining/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/ingredient-sourcing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/inventory-management-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/labor-scheduling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/loyalty-program-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/market-feasibility/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/marketing-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/menu-costing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/menu-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/menu-engineering/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/online-ordering-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/opening-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/par-level-setting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/peak-hour-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/portion-control/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/recipe-scaling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/recipe-standardization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/restaurant-business-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/review-management-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/sanitation-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/service-standards/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/social-media-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/staff-training-restaurant/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/temperature-log/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/vendor-negotiation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/waste-reduction/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/food-beverage/wine-pairing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/appointment-reminder/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/billing-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/breach-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/care-coordination/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/care-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/chronic-disease-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/clinical-trial-recruitment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/coding-accuracy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/condition-explainer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/consent-form/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/corporate-wellness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/credentialing-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/discharge-instructions/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/follow-up-message/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/health-content-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/hipaa-compliance-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/infection-control/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/informed-consent/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/insurance-verification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/medical-history-form/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/mental-health-resources-health/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/online-reputation-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-acquisition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-communication/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-education-material/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-intake-form/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-portal-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/patient-satisfaction-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/population-health-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/practice-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/practice-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/preventive-care-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/privacy-notice/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/provider-enrollment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/quality-metrics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/referral-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/referral-program-health/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/research-protocol-summary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/revenue-cycle-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/review-response-healthcare/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/safety-protocol/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/staff-training-healthcare/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/telehealth-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/testimonial-request-health/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/transition-of-care/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/treatment-plan-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/virtual-visit-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/healthcare/wellness-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/30-60-90-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/all-hands-agenda/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/attrition-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/benefits-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/buddy-system-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/candidate-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/career-development-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/coaching-conversation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/compensation-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/conflict-resolution/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/contractor-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/culture-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/culture-values-definition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/dei-metrics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/dei-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/employee-engagement-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/employee-handbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/employer-brand/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/exit-interview/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/feedback-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/grievance-procedure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/hiring-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/hr-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/hybrid-work-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/inclusive-hiring-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/individual-development-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/interview-question-bank/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/interview-scorecard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/job-description/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/job-posting-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/mediation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/mental-health-resources/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/offer-negotiation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/offsite-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/onboarding-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/organizational-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/peer-review-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/people-analytics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/performance-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/pip-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/pulse-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/recognition-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/reference-check-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/remote-work-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/role-definition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/salary-negotiation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/self-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/structured-interview-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/succession-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/team-building-activity/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/team-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/temp-to-perm-process/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/training-needs-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/training-program-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/wellness-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/workforce-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/hr/workshop-facilitator-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/acceptable-use-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/annual-report-compliance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/anti-bribery-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/audit-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/board-resolution/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/breach-notification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/bylaws-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/ccpa-compliance-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/cease-and-desist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/code-of-conduct/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/compliance-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/compliance-training-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/conflict-of-interest-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/consent-resolution/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/contractor-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/cookie-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/copyright-notice/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/data-processing-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/data-retention-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/demand-letter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/dmca-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/dpia-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/employment-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/gdpr-compliance-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/gdpr-data-mapping/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/incident-response-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/insider-trading-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/insurance-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/ip-assignment-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/joint-venture-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/lease-review-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/licensing-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/litigation-hold/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/meeting-minutes/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/mou-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/nda-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/offer-letter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/operating-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/partnership-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/patent-prior-art-search/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/privacy-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/refund-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/regulatory-change-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/regulatory-filing-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/risk-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/service-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/settlement-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/shareholder-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/shipping-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/termination-letter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/terms-of-service/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/trademark-filing-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/vendor-contract-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/legal/whistleblower-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/account-based-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/attribution-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/audience-persona/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/audience-segmentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/b2b-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/b2c-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/back-to-school-campaign/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/brand-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/brand-guidelines/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/brand-messaging-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/brand-positioning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/brand-voice-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/campaign-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/campaign-retrospective/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/campaign-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/channel-mix-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/channel-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/co-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/community-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/competitor-ad-teardown/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/competitor-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/content-marketing-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/conversion-funnel-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/crisis-communication-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/cross-promotion-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/customer-journey-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/d2c-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/demand-generation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/drip-campaign-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/elevator-pitch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/event-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/geo-targeting-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/go-to-market-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/growth-experiment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/guerrilla-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/holiday-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/influencer-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/influencer-outreach/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/influencer-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/kpi-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/launch-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/launch-timeline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/lead-magnet-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/local-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/loyalty-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/market-research/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/market-sizing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-automation-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-budget/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-calendar/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-funnel-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/marketing-stack-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/martech-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/media-kit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/media-pitch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/messaging-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/multi-market-launch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/partnership-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/pr-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/press-release/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/product-launch-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/rebranding-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/referral-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/retargeting-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/seasonal-campaign/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/sponsorship-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/tagline-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/thought-leadership-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/touchpoint-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/trade-show-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/unique-selling-proposition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/value-proposition-canvas/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/vendor-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/viral-loop-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/marketing/webinar-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/advertising-rate-card/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/article-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/audience-growth-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/audience-insights/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/book-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/book-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/breaking-news-protocol/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/chapter-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-analytics-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-distribution/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-licensing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-performance/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-strategy-media/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/content-syndication/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/contributor-guidelines/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/correction-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/cross-promotion/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/editorial-calendar/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/editorial-guidelines/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/editorial-style-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/fact-checking-process/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/feature-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/freelancer-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/interview-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/interview-questions/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/interview-transcript/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/investigative-piece/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/live-blog/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/live-event-coverage/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/media-kit-creator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/newsletter-growth/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/newsletter-launch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/newsletter-monetization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/paywall-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/podcast-format-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/podcast-launch-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/podcast-monetization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/republishing-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/social-media-promotion/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/sponsorship-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/submission-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/subscriber-acquisition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/video-editing-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/video-production-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/media/youtube-channel-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/990-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/advocacy-campaign/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/annual-appeal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/annual-report-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/auction-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/audit-prep-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/board-meeting-agenda/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/board-orientation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/board-recruitment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/case-for-support/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/cause-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/compliance-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/conflict-of-interest/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/corporate-partnership/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/corporate-sponsorship/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/crowdfunding-campaign/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/donation-thank-you/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/donor-cultivation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/donor-retention/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/donor-segmentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/event-fundraiser/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/financial-report-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/fundraising-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/fundraising-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/gala-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/gift-acceptance-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/giving-tuesday/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/grant-budget/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/grant-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/grant-research/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/grassroots-mobilization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/impact-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/lapsed-donor-reactivation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/logic-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/major-gift-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/needs-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/nonprofit-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/outcomes-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/peer-to-peer-fundraising/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/policy-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/program-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/program-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/storytelling-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/strategic-plan-nonprofit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/theory-of-change/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/volunteer-onboarding/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recognition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recruitment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/action-item-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/automation-opportunity-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/bottleneck-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/business-continuity-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/capacity-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/change-management-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/communication-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/contingency-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/cross-functional-alignment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/decision-log/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/defect-tracking/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/delegation-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/disaster-recovery-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/efficiency-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/executive-summary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/goal-setting-workshop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/handover-document/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/incident-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/inventory-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/kanban-board-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/kpi-definition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/lean-six-sigma/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/lessons-learned/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/logistics-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/meeting-agenda/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/meeting-notes/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/offboarding-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/okr-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/onboarding-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/operating-rhythm/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/post-mortem/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/process-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/process-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/progress-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/project-charter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/project-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/project-timeline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/quality-assurance-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/quality-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/raci-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/resource-allocation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/responsibility-assignment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/risk-mitigation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/risk-register/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/sop-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/sprint-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/sprint-retrospective/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/sprint-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/stakeholder-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/status-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/supply-chain-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/team-charter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/tech-stack-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/time-tracking-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/tool-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/vendor-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/vendor-onboarding/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/vendor-scorecard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/workflow-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/operations/workload-balancing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/ab-test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/acceptance-criteria/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/activation-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/aha-moment-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/analytics-implementation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/api-product-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/beta-program-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/board-product-update/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/bug-triage/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/changelog-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/competitive-product-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/data-taxonomy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/deprecation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/early-adopter-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/ecosystem-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/empathy-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/event-tracking-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/experiment-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/faq-builder/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feature-comparison-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feature-flag-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feature-prioritization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feature-request-triage/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feature-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/feedback-taxonomy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/freemium-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/impact-effort-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/job-to-be-done/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/knowledge-base-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/migration-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/north-star-metric/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/persona-creation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/pirate-metrics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/platform-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/positioning-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/prd-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/pricing-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-council-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-documentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-health-check/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-launch-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-metrics-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-onboarding-flow/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-one-pager/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-principles/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-retrospective/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/product-vision/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/release-notes-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/release-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/rice-scoring/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/stakeholder-update/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/technical-debt-prioritization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/technology-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/trial-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/usability-test-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/user-interview-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/user-journey-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/user-research-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/product/user-story/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/annual-goals/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/bio-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/book-summary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/boundary-setting/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/burnout-prevention/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/career-development/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/career-pivot-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/consulting-rate-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/cover-letter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/daily-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/decision-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/deep-work-blocks/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/delegation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/eisenhower-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/email-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/email-template-library/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/energy-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/follow-up-system/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/freelance-proposal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/goal-setting-okr/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/gratitude-practice/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/habit-stack-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/habit-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/inbox-zero-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/journal-prompts/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/learning-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/linkedin-profile-rewrite/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/linkedin-recommendation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/meeting-agenda-personal/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/meeting-notes-summary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/meeting-optimizer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/mit-method/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/networking-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/outsourcing-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/peak-performance-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/personal-brand-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/presentation-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/priority-matrix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/project-breakdown/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/pros-cons-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/public-speaking-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/quarterly-goals/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/reflection-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/relationship-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/resume-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/routine-optimizer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/salary-negotiation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/side-project-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/skill-acquisition-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/storytelling-framework/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/task-decomposition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/time-blocking/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/virtual-assistant-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/weekly-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/weighted-scoring/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/work-breakdown-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/productivity/work-life-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/1031-exchange-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/airbnb-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/asset-allocation-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/buyer-consultation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/buyer-needs-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/cap-rate-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/cash-on-cash-return/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/commercial-property-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/comparative-market-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/construction-budget/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/counter-offer-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/depreciation-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/development-feasibility/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/exit-strategy-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/farming-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/investment-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/just-sold-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/lease-agreement-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/listing-description/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/listing-photography-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/listing-presentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/maintenance-schedule/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/market-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/market-update-newsletter/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/negotiation-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/neighborhood-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/offer-letter-real-estate/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/office-lease-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/open-house-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/portfolio-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/project-timeline-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/property-inspection/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/property-listing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/property-management-sop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/real-estate-marketing-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/referral-program-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/rental-property-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/retail-space-evaluation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/seller-consultation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/showing-feedback/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/sphere-of-influence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/tax-strategy-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/tenant-screening/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/vacation-rental-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/real-estate/vendor-management-re/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/account-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/affiliate-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/boardroom-presentation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/breakup-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/business-case/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/buyer-persona-sales/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/cadence-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/case-study-sales/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/channel-partner-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/churn-prevention/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/cold-call-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/cold-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/cold-linkedin-message/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/commission-structure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/competitor-battlecard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/crm-setup-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/cross-sell-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/deal-qualification/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/deal-scoring/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/demo-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/discovery-call-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/executive-sponsor-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/expansion-revenue-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/follow-up-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/forecast-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/ideal-customer-profile/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/incentive-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/lead-scoring-model/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/objection-handling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/onboarding-sales-rep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/one-pager/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/pipeline-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/pipeline-stage-definitions/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/pricing-negotiation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/procurement-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/proposal-writer/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/quarterly-business-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/quota-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/re-engagement-email/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/referral-ask/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/renewal-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/reseller-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/rfp-response-sales/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/roi-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/role-play-scenario/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-automation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-contract/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-enablement-content/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-kpi-tracker/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-meeting-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-pitch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-process-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sales-training-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sell-sheet/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/sequence-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/spiff-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/statement-of-work/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/strategic-account-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/target-account-list/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/territory-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/upsell-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/vendor-questionnaire/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/sales/win-loss-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/app-store-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/backlink-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/broken-link-building/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/canonical-tag-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/category-page-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/competitor-seo-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/content-decay-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/content-refresh-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/content-seo-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/conversion-tracking-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/core-web-vitals-fix/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/crawl-budget-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/digital-pr-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/ecommerce-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/featured-snippet-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/google-analytics-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/google-business-profile/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/google-search-console-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/guest-post-outreach/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/haro-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/header-tag-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/hreflang-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/image-alt-text-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/internal-linking-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/international-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/keyword-clustering/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/keyword-gap-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/keyword-research/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/link-building-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/local-citation-building/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/local-keyword-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/local-link-building/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/local-seo-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/long-tail-keyword-finder/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/meta-description-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/meta-title-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/multilingual-seo-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/on-page-seo-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/podcast-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/product-page-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/question-keyword-research/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/redirect-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/review-generation-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/robots-txt-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/schema-markup-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/search-intent-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/seo-content-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/seo-content-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/seo-forecast/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/seo-reporting-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/seo-roadmap/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/serp-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/site-speed-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/technical-seo-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/topical-authority-map/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/xml-sitemap-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/seo/youtube-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/bluesky-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/brand-ambassador-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/community-guidelines/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/creator-partnership/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/cross-platform-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/employee-advocacy-program/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/engagement-rate-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/executive-social-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/facebook-event-promotion/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/facebook-group-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/facebook-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/follower-growth-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/influencer-collaboration-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-bio-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-carousel/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-hashtag-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-reel-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/instagram-story-sequence/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-article/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-carousel/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-company-page/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-outreach/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/linkedin-profile-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/mastodon-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/negative-comment-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/pinterest-board-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/pinterest-pin/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/pinterest-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/platform-migration-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/reddit-ama-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/reddit-community-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/reddit-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/review-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/sentiment-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-content-calendar/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-contest/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-listening-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-media-bio-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-media-crisis-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-media-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-media-response/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-selling/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/social-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/threads-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-content-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-duet-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-hook-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-series-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/tiktok-trend-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/trend-report/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-engagement-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-growth-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-profile-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-spaces-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/twitter-thread/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/ugc-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/user-generated-content-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/viral-content-formula/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-channel-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-description-seo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-playlist-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-shorts-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-title-thumbnail/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/social-media/youtube-video-outline/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/accelerator-application/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/acquisition-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/advisory-board-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/board-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/bootstrap-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/brand-name-generator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/build-measure-learn/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/business-model-canvas/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/business-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/cap-table-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/co-founder-agreement/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/competitive-landscape/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/culture-code/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/customer-discovery/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/data-room-setup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/defensibility-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/distribution-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/domain-name-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/due-diligence-prep/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/equity-split/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/exit-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/fundraising-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/growth-experiment-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/growth-metrics/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/growth-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/hiring-first-ten/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/incorporation-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/investor-outreach/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/investor-pitch-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/investor-target-list/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/investor-update-template/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/ipo-readiness/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/kill-criteria/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/lean-canvas/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/market-validation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/marketplace-launch/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/mentor-outreach/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/moat-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/monetization-strategy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/mvp-definition/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/mvp-feature-list/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/one-page-memo/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/partnership-strategy-startup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/pitch-deck/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/pivot-assessment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/pivot-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/pmf-survey/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/pricing-experiment/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/problem-validation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/product-market-fit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/remote-startup-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/retention-analysis-startup/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/revenue-model-design/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/side-project-validation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/solopreneur-playbook/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/startup-legal-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/startup-metrics-dashboard/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/team-building/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/term-sheet-negotiation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/startup/trademark-search/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/accommodation-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/activity-planner/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/adventure-travel-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/airbnb-listing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/bleisure-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/budget-travel-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/catering-menu/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/conference-planning/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/corporate-travel-policy/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/cost-comparison/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/crisis-management-hospitality/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/day-by-day-itinerary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/destination-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/destination-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/dining-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/dynamic-pricing-hospitality/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/eco-tourism-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/emergency-procedure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/event-planning-venue/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/excursion-brief/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/family-vacation-planner/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/food-tour-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/front-desk-procedure/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/group-travel-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/guest-experience-audit/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/guest-feedback-analysis/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/guest-persona/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/health-safety-protocol/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/honeymoon-planner/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/hotel-operations-sop/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/hotel-review/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/housekeeping-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/itinerary-planner/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/loyalty-program-hospitality/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/luxury-travel-concierge/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/multi-city-itinerary/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/occupancy-optimization/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/packing-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/responsible-travel/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/restaurant-recommendation/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/revenue-management/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/seasonal-promotion/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/service-recovery/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/solo-travel-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/sustainability-plan-travel/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/tour-guide-script/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/tourism-marketing/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/travel-blog-post/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/travel-budget-calculator/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/travel-document-checklist/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/travel-photography-guide/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/travel-savings-plan/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/upsell-strategy-hospitality/SKILL.md create mode 100644 clowdex-download/.claude/.claude/skills/travel/visa-requirements/SKILL.md create mode 100644 clowdex-download/.claude/.mcp.json create mode 100644 clowdex-download/.claude/CLAUDE.local.md create mode 100644 clowdex-download/.claude/CLAUDE.md create mode 100644 clowdex-download/.claude/SETUP.md create mode 100644 clowdex-download/.claude/Scratchpad.md create mode 100644 clowdex-download/.claude/Task Board.md create mode 100644 docker-compose.yml create mode 100644 docs/schema.md create mode 100644 frontend/package.json create mode 100644 frontend/vite.config.ts diff --git a/.claude/knowledge-base.md b/.claude/knowledge-base.md new file mode 100644 index 0000000..f24df1d --- /dev/null +++ b/.claude/knowledge-base.md @@ -0,0 +1,55 @@ +# Knowledge Base — C-Stone Invoice Check + +## Stack-Entscheidung + +**FastAPI + PostgreSQL + React** gewählt weil: +- SaaS-Architektur für langfristige Erweiterbarkeit +- FastAPI: Async, automatische OpenAPI-Dokumentation +- PostgreSQL: Zuverlässige Datenpersistenz für Rechnungsdaten +- React: Moderne Frontend-Entwicklung + +**PyMuPDF** gewählt für PDF-Extraktion: +- Läuft vollständig lokal +- Keine Datenverlust Gefahr (DSGVO-konform) +- Schnell und zuverlässig für Text-Extraktion +- Gute Erkennung von Steuerangaben in Rechnungen + +## DSGVO-Status +**nein** — Rechnungsdaten (Betrag,Datum,Absender) gelten nicht als personenbezogene Daten im Sinne der DSGVO +AWS Bedrock Region: eu-central-1 (Frankfurt) — Pflicht bei Bedrock-Nutzung + +## Bekannte Fallstricke (C-Stone-Standard) +- SQLAlchemy Enum: Namen in GROSSBUCHSTABEN, nicht Values +- SeaTable: Zugriff NUR über Flask Microservice, nicht direkt über n8n +- .env NIEMALS committen, NIEMALS in Nextcloud-Sync +- IMAP-Authentifizierung: App-Passwords statt Hauptpasswort verwenden + +## Ablauf-Logik + +### Email-Filterung +1. IMAP-Verbindung zu Strato/Gmail aufbauen +2. Emails mit Stichworten filtern: "Rechnung", "Invoice", "Receipt" +3. Anhänge extrahieren (PDF/DOC) +4. PDF mit PyMuPDF scannen +5. Steuerangaben erkennen (Mehrwertsteuer, Umsatzsteuer, VAT) +6. Entscheidung: mit/ohne Steuer + +### Dateiablage (Evo-X2) +``` +Rechnungen/ +├── 2025/ +│ ├── mit MwSt/ +│ └── ohne MwSt/ +└── 2026/ + ├── mit MwSt/ + └── ohne MwSt/ +``` + +### Excel-Dokumentation +- Spalten: Datum, Rechnungsausteller, Betrag, Umsatzsteuer, Steuerart, Dateipfad +- Format: xlsx (Excel 2007+) + +## Entscheidungen +- Automatische Speicherung (keine manuelle Bestätigung nötig) +- Nur speichern, keine Weiterleitung +- xlsx-Format für Excel-Tabelle diff --git a/.claude/memory.md b/.claude/memory.md new file mode 100644 index 0000000..24c680e --- /dev/null +++ b/.claude/memory.md @@ -0,0 +1,25 @@ +# Memory — C-Stone Invoice Check + +## Aktuelles Projekt: C-Stone Invoice Check +- **Typ:** SaaS-App +- **Gestartet:** 2026-07-24 +- **DSGVO-relevant:** nein +- **Beschreibung:** Email-Filter für Rechnungen mit PDF-Scanning, lokale Ablage auf Evo-X2, Excel-Dokumentation +- **Stack:** FastAPI + PostgreSQL + React + PyMuPDF +- **Ablageort:** Evo-X2 ( lokales Laufwerk ) +- **GitHub:** https://github.com/c-stone/c-stone-invoice-check + +## Aktuelle Phase: 1 — Scope & Setup ✅ → Phase 2 — Architektur + +## Offene Punkte: +- [ ] Architektur finalisieren (Phase 2) +- [ ] docker-compose.yml mit Traefik-Labels erstellen +- [ ] Datenbankschema in docs/schema.md entwerfen + +## Mail-Provider Konfiguration +- Strato + Gmail (IMAP Zugriff) +- Evo-X2 als Ablageserver + +## PDF-Verarbeitung +- PyMuPDF (fitz) für lokal laufende Text-Extraktion +- Keine Daten verlassen den Server diff --git a/.env.example b/.env.example new file mode 100644 index 0000000..6b54605 --- /dev/null +++ b/.env.example @@ -0,0 +1,32 @@ +# Datenbank +DATABASE_URL=postgresql://user:password@localhost:5432/invoice_check +REDIS_URL=redis://localhost:6379 + +# Auth +SECRET_KEY=your-secret-key-here +ALGORITHM=HS256 +ACCESS_TOKEN_EXPIRE_MINUTES=30 + +# AWS Bedrock (DSGVO: eu-central-1) +AWS_ACCESS_KEY_ID=your-key-here +AWS_SECRET_ACCESS_KEY=your-secret-here +AWS_DEFAULT_REGION=eu-central-1 + +# Mail-Server (Strato + Gmail) +IMAP_HOST=imap.strato.de +IMAP_PORT=993 +IMAP_USER=your-email@domain.de +IMAP_PASSWORD=your-app-password + +# Gmail (optional, falls auch Gmail genutzt wird) +GMAIL_IMAP_HOST=imap.gmail.com +GMAIL_IMAP_PORT=993 +GMAIL_IMAP_USER=your-email@gmail.com +GMAIL_IMAP_PASSWORD=your-app-password + +# Ablageort (Evo-X2) +INVOICE_STORAGE_PATH=/Volumes/Evo-X2/Rechnungen + +# App +ENVIRONMENT=development +PORT=8001 diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..b84e36f --- /dev/null +++ b/.gitignore @@ -0,0 +1,15 @@ +.env +.env.* +!.env.example +*.pem +*.key +node_modules/ +__pycache__/ +*.pyc +.DS_Store +venv/ +.venv/ +dist/ +build/ +*.db +*.sqlite diff --git a/.nextcloudignore b/.nextcloudignore new file mode 100644 index 0000000..d74fd6f --- /dev/null +++ b/.nextcloudignore @@ -0,0 +1,12 @@ +node_modules/ +__pycache__/ +.env +.env.* +*.pem +*.db +*.sqlite +venv/ +.venv/ +dist/ +build/ +.git/ diff --git a/README.md b/README.md new file mode 100644 index 0000000..2d6ad38 --- /dev/null +++ b/README.md @@ -0,0 +1,48 @@ +# C-Stone Invoice Check + +## Zweck + +KI-gestütztes Email-Filter-System für Rechnungen mit automatischer PDF-Scanning, lokaler Ablage auf Evo-X2 und Excel-Dokumentation. + +## Was das System macht + +1. **Email-Filterung** per IMAP (Strato + Gmail) nach Stichworten: "Rechnung", "Invoice", "Receipt" +2. **Anhang-Extraktion** (PDF/DOC) aus erkannten Emails +3. **PDF-Scanning** mit PyMuPDF für Text-Extraktion +4. **Steuer-Erkennung**: Unterscheidung zwischen "mit MwSt" / "ohne MwSt" / "Umsatzsteuer" / "VAT" +5. **Lokale Ablage** auf Evo-X2: + ``` + Rechnungen/ + ├── 2025/ + │ ├── mit MwSt/ + │ └── ohne MwSt/ + └── 2026/ + ├── mit MwSt/ + └── ohne MwSt/ + ``` +6. **Excel-Dokumentation** mit Spalten: Datum, Rechnungsausteller, Betrag, Umsatzsteuer, Steuerart, Dateipfad + +## Voraussetzungen + +```bash +pip3 install fastapi uvicorn python-dotenv sqlalchemy psycopg2-binary openpyxl pymupdf +``` + +## Konfiguration + +1. `.env.example` nach `.env` kopieren +2. IMAP-Credentials für Strato/Gmail eintragen (App-Passwords verwenden!) +3. Ablagepfad auf Evo-X2 anpassen (`INVOICE_STORAGE_PATH`) + +## Ablauf + +1. System starten: `uvicorn backend.main:app --reload --port 8001` +2. Frontend öffnen: `http://localhost:5173` +3. IMAP-Verbindung wird periodisch geprüft +4. Neue Rechnungen werden automatisch verarbeitet und gespeichert + +## DSGVO + +- Alle Daten bleiben lokal auf Evo-X2 +- Keine Datenverarbeitung in der Cloud +- PyMuPDF läuft vollständig lokal diff --git a/Task Board.md b/Task Board.md new file mode 100644 index 0000000..b74ea1d --- /dev/null +++ b/Task Board.md @@ -0,0 +1,48 @@ +# Task Board — C-Stone Invoice Check + +## 📋 Backlog + +- [ ] Dockerfile.backend erstellen +- [ ] Dockerfile frontend (React/Vite) erstellen +- [ ] frontend/src/App.tsx erstellen +- [ ] frontend/src/main.tsx erstellen +- [ ] frontend/vite.config.ts konfigurieren +- [ ] frontend/package.json mit Dependencies +- [ ] .gitignore prüfen und anpassen +- [ ] .env.example mit echten Platzhaltern +- [ ] README.md mit Detaillierung erweitern +- [ ] Alembic Migration initialisieren +- [ ] pytest Setup mit conftest.py + +## 🚀 Aktuell (Phase 2 — Architektur) + +- [ ] docker-compose.yml mit Traefik-Labels erstellen +- [ ] Datenbankschema in docs/schema.md entwerfen (✅ erledigt) +- [ ] FastAPI Grundstruktur mit Health-Endpunkt (✅ erledigt) +- [ ] Backend Router implementieren (emails.py, invoices.py - ✅ erledigt) +- [ ] PDF-Scanning mit PyMuPDF implementieren (✅ erledigt) +- [ ] Excel-Export mit openpyxl implementieren (✅ erledigt) +- [ ] Frontend Grundstruktur (Vite + React) +- [ ] IMAP-Verbindung testen (Strato + Gmail) +- [ ] PDF-Verarbeitung lokal testen +- [ ] Evo-X2 Ablagepfad konfigurieren + +## ✅ Erledigt + +- [x] Projektordner angelegt +- [x] Base Project kopiert +- [x] SaaS-Struktur erstellt (backend/, frontend/, docs/) +- [x] requirements.txt mit Dependencies +- [x] docker-compose.yml erstellt +- [x] .env.example mit Platzhaltern +- [x] .gitignore und .nextcloudignore +- [x] README.md initialisiert +- [x] memory.md und knowledge-base.md +- [x] Database-Models (Invoice, EmailLog, InvoiceDetail, User) +- [x] Email Router (IMAP Search, Filterung) +- [x] Invoice Router (PDF-Scan, Tax-Detection, Excel-Export) +- [x] Datenbankschema dokumentiert (docs/schema.md) + +## 🔒 Blockiert + +- diff --git a/backend/__init__.py b/backend/__init__.py new file mode 100644 index 0000000..e827d13 --- /dev/null +++ b/backend/__init__.py @@ -0,0 +1 @@ +# Backend Package diff --git a/backend/auth.py b/backend/auth.py new file mode 100644 index 0000000..6175d93 --- /dev/null +++ b/backend/auth.py @@ -0,0 +1,96 @@ +""" +C-Stone Invoice Check — Authentifizierung +JWT-basierte Auth mit PyJWT +""" + +import os +from datetime import datetime, timedelta +from typing import Optional +from jose import JWTError, jwt +from passlib.context import CryptContext +from fastapi import Depends, HTTPException, status +from fastapi.security import OAuth2PasswordBearer +from sqlalchemy.orm import Session +from sqlalchemy import Column, Integer, String, Boolean, DateTime + +from backend.database import get_db + +# Konfiguration +SECRET_KEY = os.getenv("SECRET_KEY", "your-secret-key-change-in-production") +ALGORITHM = "HS256" +ACCESS_TOKEN_EXPIRE_MINUTES = 30 + +# Hash-Kontext +pwd_context = CryptContext(schemes=["bcrypt"], deprecated="auto") + +# OAuth2 +oauth2_scheme = OAuth2PasswordBearer(tokenUrl="/auth/token") + +# Router +from fastapi import APIRouter +router = APIRouter() + + +class User(Base): + __tablename__ = "users" + + id = Column(Integer, primary_key=True, index=True) + username = Column(String, unique=True, index=True) + hashed_password = Column(String) + is_active = Column(Boolean, default=True) + created_at = Column(DateTime, default=datetime.utcnow) + + +def verify_password(plain_password: str, hashed_password: str) -> bool: + """Prüft Passwort gegen Hash""" + return pwd_context.verify(plain_password, hashed_password) + + +def get_password_hash(password: str) -> str: + """Erstellt Hash aus Passwort""" + return pwd_context.hash(password) + + +def create_access_token(data: dict, expires_delta: Optional[timedelta] = None) -> str: + """Erstellt JWT Token""" + to_encode = data.copy() + if expires_delta: + expire = datetime.utcnow() + expires_delta + else: + expire = datetime.utcnow() + timedelta(minutes=15) + to_encode.update({"exp": expire}) + encoded_jwt = jwt.encode(to_encode, SECRET_KEY, algorithm=ALGORITHM) + return encoded_jwt + + +def authenticate_user(db: Session, username: str, password: str) -> Optional[User]: + """Authentifiziert Benutzer""" + user = db.query(User).filter(User.username == username).first() + if not user: + return None + if not verify_password(password, user.hashed_password): + return None + return user + + +async def get_current_user( + token: str = Depends(oauth2_scheme), + db: Session = Depends(get_db) +) -> User: + """Holt aktuellen Benutzer aus Token""" + credentials_exception = HTTPException( + status_code=status.HTTP_401_UNAUTHORIZED, + detail="Could not validate credentials", + headers={"WWW-Authenticate": "Bearer"}, + ) + try: + payload = jwt.decode(token, SECRET_KEY, algorithms=[ALGORITHM]) + username: str = payload.get("sub") + if username is None: + raise credentials_exception + except JWTError: + raise credentials_exception + user = db.query(User).filter(User.username == username).first() + if user is None: + raise credentials_exception + return user diff --git a/backend/database.py b/backend/database.py new file mode 100644 index 0000000..84351ea --- /dev/null +++ b/backend/database.py @@ -0,0 +1,40 @@ +""" +C-Stone Invoice Check — Datenbankkonfiguration +SQLAlchemy Engine und Session Management +""" + +import os +from sqlalchemy import create_engine +from sqlalchemy.orm import sessionmaker, declarative_base +from dotenv import load_dotenv + +# Load environment variables +load_dotenv() + +DATABASE_URL = os.getenv( + "DATABASE_URL", + "postgresql://postgres:postgres@localhost:5432/invoice_check" +) + +# Engine erstellen +engine = create_engine( + DATABASE_URL, + echo=False, # SQL-Logging (False für Production) + pool_pre_ping=True, # Verbindungs-Check + pool_size=10, + max_overflow=20 +) + +# Session +SessionLocal = sessionmaker(autocommit=False, autoflush=False, bind=engine) + +# Base für Models +Base = declarative_base() + +# Dependency für FastAPI +def get_db(): + db = SessionLocal() + try: + yield db + finally: + db.close() diff --git a/backend/main.py b/backend/main.py new file mode 100644 index 0000000..665fd5d --- /dev/null +++ b/backend/main.py @@ -0,0 +1,61 @@ +""" +C-Stone Invoice Check — Hauptanwendung +FastAPI Backend für Email-Filterung und Rechnungsverarbeitung +""" + +from fastapi import FastAPI, Depends, HTTPException +from fastapi.middleware.cors import CORSMiddleware +from fastapi.responses import JSONResponse +from sqlalchemy.orm import Session + +from backend.database import get_db, engine, Base +from backend import auth + +# Models importieren für Alembic +from backend.models import Invoice, InvoiceDetail + +# Routers +from backend.routers import emails, invoices + +# App erstellen +app = FastAPI( + title="C-Stone Invoice Check API", + description="Email-Filterung und Rechnungsverarbeitung", + version="1.0.0", + docs_url="/docs", + redoc_url="/redoc" +) + +# CORS +app.add_middleware( + CORSMiddleware, + allow_origins=["*"], + allow_credentials=True, + allow_methods=["*"], + allow_headers=["*"], +) + +# Health Check +@app.get("/health") +async def health_check(db: Session = Depends(get_db)): + """Health Check Endpoint""" + try: + db.execute("SELECT 1") + return {"status": "healthy", "database": "connected"} + except Exception as e: + return {"status": "unhealthy", "database": "disconnected", "error": str(e)} + +# Initialisierung +@app.on_event("startup") +async def startup_event(): + """Datenbank erstellen bei Start""" + Base.metadata.create_all(bind=engine) + +# Router einbinden +app.include_router(auth.router, prefix="/auth", tags=["authentication"]) +app.include_router(emails.router, prefix="/emails", tags=["emails"]) +app.include_router(invoices.router, prefix="/invoices", tags=["invoices"]) + +if __name__ == "__main__": + import uvicorn + uvicorn.run(app, host="0.0.0.0", port=8001) diff --git a/backend/models.py b/backend/models.py new file mode 100644 index 0000000..a685bea --- /dev/null +++ b/backend/models.py @@ -0,0 +1,103 @@ +""" +C-Stone Invoice Check — Datenbankmodelle +SQLAlchemy ORM Modelle für Rechnungen und Emails +""" + +from datetime import datetime +from sqlalchemy import Column, Integer, String, DateTime, Float, Boolean, Text, JSON +from sqlalchemy.ext.declarative import declarative_base + +Base = declarative_base() + + +class Invoice(Base): + """ + Tabelle: Rechnungen + Speichert die Metadaten jeder verarbeiteten Rechnung + """ + __tablename__ = "invoices" + + id = Column(Integer, primary_key=True, index=True) + email_id = Column(String, index=True) # IMAP UID der Original-Email + email_subject = Column(String, nullable=True) + email_from = Column(String, nullable=True) + email_date = Column(DateTime, nullable=True) + + # Rechnungsdaten + invoice_number = Column(String, index=True, nullable=True) + invoice_date = Column(DateTime, nullable=True) + invoice_amount = Column(Float, nullable=True) + invoice_tax_amount = Column(Float, nullable=True) + invoice_tax_rate = Column(Float, nullable=True) # z.B. 0, 0.19, 0.16 + invoice_tax_type = Column(String, nullable=True) # "MwSt", "Umsatzsteuer", "VAT", "ohne" + + # Absender/Empfänger + issuer_name = Column(String, nullable=True) + issuer_address = Column(Text, nullable=True) + + # Dateipfad (Evo-X2) + file_path = Column(String, nullable=True) + file_name = Column(String, nullable=True) + storage_year = Column(Integer, nullable=True) + storage_path = Column(String, nullable=True) # z.B. "2025/ohne MwSt" + + # Verarbeitungsstatus + processed = Column(Boolean, default=False) + processing_error = Column(Text, nullable=True) + confidence_score = Column(Float, nullable=True) # 0.0 - 1.0 + + created_at = Column(DateTime, default=datetime.utcnow) + updated_at = Column(DateTime, default=datetime.utcnow, onupdate=datetime.utcnow) + + def __repr__(self): + return f"" + + +class EmailLog(Base): + """ + Tabelle: Email Logs + Protokolliert jede verarbeitete Email + """ + __tablename__ = "email_logs" + + id = Column(Integer, primary_key=True, index=True) + email_id = Column(String, unique=True, index=True) # IMAP UID + email_subject = Column(String, nullable=True) + email_from = Column(String, nullable=True) + email_date = Column(DateTime, nullable=True) + email_folder = Column(String, nullable=True) # z.B. "INBOX", "Gesendet" + + # Filterergebnis + matched_keywords = Column(JSON, nullable=True) # Liste von Stichworten + has_attachment = Column(Boolean, default=False) + attachment_type = Column(String, nullable=True) # "pdf", "doc", "docx", "unknown" + + # Verarbeitung + processed = Column(Boolean, default=False) + processing_result = Column(String, nullable=True) # "invoice_found", "not_an_invoice", "error" + invoice_id = Column(Integer, nullable=True) # Verweis auf Invoice-Tabelle + + created_at = Column(DateTime, default=datetime.utcnow) + + def __repr__(self): + return f"" + + +class InvoiceDetail(Base): + """ + Tabelle: Rechnungsdetails (erweiterte Informationen) + Speichert JSON-basierte erweiterte Daten + """ + __tablename__ = "invoice_details" + + id = Column(Integer, primary_key=True, index=True) + invoice_id = Column(Integer, nullable=False, index=True) + raw_text = Column(Text, nullable=True) # Extrahierter PDF-Text + parsed_data = Column(JSON, nullable=True) # Geparste Daten als JSON + confidence_breakdown = Column(JSON, nullable=True) # Einzelne Confidence-Scores + processing_notes = Column(Text, nullable=True) + + created_at = Column(DateTime, default=datetime.utcnow) + + def __repr__(self): + return f"" diff --git a/backend/requirements.txt b/backend/requirements.txt new file mode 100644 index 0000000..4a636aa --- /dev/null +++ b/backend/requirements.txt @@ -0,0 +1,26 @@ +# FastAPI und Server +fastapi==0.115.0 +uvicorn[standard]==0.30.0 +python-multipart==0.0.9 + +# Datenbank +sqlalchemy==2.0.32 +psycopg2-binary==2.9.9 +alembic==1.13.1 + +# Authentifizierung +python-jose[cryptography]==3.3.0 +passlib[bcrypt]==1.7.4 + +# PDF-Verarbeitung (PyMuPDF - lokal laufend) +pymupdf==1.24.10 + +# Excel-Verarbeitung +openpyxl==3.1.5 + +# Mail (IMAP) +imaplib2==3.5 + +# Allgemein +python-dotenv==1.0.1 +boto3==1.35.0 diff --git a/backend/routers/__init__.py b/backend/routers/__init__.py new file mode 100644 index 0000000..ac5013a --- /dev/null +++ b/backend/routers/__init__.py @@ -0,0 +1 @@ +# Router Package diff --git a/backend/routers/emails.py b/backend/routers/emails.py new file mode 100644 index 0000000..a99a8ff --- /dev/null +++ b/backend/routers/emails.py @@ -0,0 +1,268 @@ +""" +C-Stone Invoice Check — Email Router +IMAP Email-Verarbeitung und Filterung +""" + +import imaplib +import email +import os +from datetime import datetime +from typing import List, Optional, Dict, Any +from fastapi import APIRouter, Depends, HTTPException +from sqlalchemy.orm import Session +from email.header import decode_header + +from backend.database import get_db +from backend.models import EmailLog, Invoice + +router = APIRouter() + +# IMAP Konfiguration +IMAP_HOST = os.getenv("IMAP_HOST", "imap.strato.de") +IMAP_PORT = int(os.getenv("IMAP_PORT", 993)) +IMAP_USER = os.getenv("IMAP_USER", "") +IMAP_PASSWORD = os.getenv("IMAP_PASSWORD", "") + +# Gmail Konfiguration +GMAIL_IMAP_HOST = os.getenv("GMAIL_IMAP_HOST", "imap.gmail.com") +GMAIL_IMAP_PORT = int(os.getenv("GMAIL_IMAP_PORT", 993)) +GMAIL_IMAP_USER = os.getenv("GMAIL_IMAP_USER", "") +GMAIL_IMAP_PASSWORD = os.getenv("GMAIL_IMAP_PASSWORD", "") + +# Filter-Kriterien +INVOICE_KEYWORDS = ["rechnung", "invoice", "receipt", "bill", "factuur"] + + +def connect_imap(host: str, port: int, user: str, password: str) -> imaplib.IMAP4_SSL: + """Verbindet mit IMAP-Server""" + mail = imaplib.IMAP4_SSL(host, port) + mail.login(user, password) + return mail + + +def search_invoices(mail: imaplib.IMAP4_SSL, folder: str = "INBOX") -> List[str]: + """Sucht nach Emails mit Rechnungs-Stichworten""" + mail.select(folder) + result, data = mail.search(None, 'ALL') + if result != "OK": + return [] + + email_ids = data[0].split() + matching_ids = [] + + for email_id in email_ids: + result, msg_data = mail.fetch(email_id, '(RFC822)') + if result != "OK": + continue + + msg = email.message_from_bytes(msg_data[0][1]) + subject = msg.get("Subject", "") + from_addr = msg.get("From", "") + + # Subject decodieren + decoded_subject, encoding = decode_header(subject)[0] + if isinstance(decoded_subject, bytes): + subject = decoded_subject.decode(encoding or "utf-8") + + # Prüfen auf Keywords + subject_lower = subject.lower() + if any(kw in subject_lower for kw in INVOICE_KEYWORDS): + matching_ids.append(email_id.decode()) + + return matching_ids + + +def extract_attachments(msg: email.message.Message) -> List[Dict[str, Any]]: + """Extrahiert Anhänge aus Email""" + attachments = [] + for part in msg.walk(): + if part.get_content_maintype() == 'multipart': + continue + if part.get('Content-Disposition') is None: + continue + + filename = part.get_filename() + if filename: + decoded_filename, encoding = decode_header(filename)[0] + if isinstance(decoded_filename, bytes): + filename = decoded_filename.decode(encoding or "utf-8") + + content_type = part.get_content_type() + payload = part.get_payload(decode=True) + + attachments.append({ + "filename": filename, + "content_type": content_type, + "data": payload, + "size": len(payload) if payload else 0 + }) + + return attachments + + +@router.get("/search") +async def search_emails(db: Session = Depends(get_db)): + """Sucht nach Rechnungs-Emails bei Strato""" + results = { + "processed": 0, + "invoices_found": 0, + "errors": [] + } + + try: + mail = connect_imap(IMAP_HOST, IMAP_PORT, IMAP_USER, IMAP_PASSWORD) + + # Alle Ordner durchsuchen + for folder in ["INBOX", "Sent", "Gesendet"]: + try: + email_ids = search_invoices(mail, folder) + results[f"{folder}_count"] = len(email_ids) + + for email_id in email_ids: + # Verarbeitung auslagern + pass + + except Exception as e: + results["errors"].append(f"Folder {folder}: {str(e)}") + + mail.logout() + results["processed"] = len(email_ids) if 'email_ids' in dir() else 0 + + except Exception as e: + results["errors"].append(f"IMAP Connection failed: {str(e)}") + + return results + + +@router.get("/process/{email_id}") +async def process_email(email_id: str, db: Session = Depends(get_db)): + """Verarbeitet einzelne Email""" + # TODO: Implementierung + pass + + +@router.get("/scan-all") +async def scan_all_emails(db: Session = Depends(get_db)): + """Scant alle Emails auf Rechnungen""" + results = { + "start_time": datetime.utcnow().isoformat(), + "processed": 0, + "invoices_found": 0, + "errors": [] + } + + # Strato Mail + try: + mail = connect_imap(IMAP_HOST, IMAP_PORT, IMAP_USER, IMAP_PASSWORD) + mail.select("INBOX") + + result, data = mail.search(None, 'ALL') + if result == "OK": + email_ids = data[0].split() + + for email_id in email_ids: + email_id_str = email_id.decode() + log_entry = db.query(EmailLog).filter(EmailLog.email_id == email_id_str).first() + + if log_entry: + continue # Bereits verarbeitet + + result, msg_data = mail.fetch(email_id, '(RFC822)') + if result != "OK": + continue + + msg = email.message_from_bytes(msg_data[0][1]) + subject = msg.get("Subject", "") + from_addr = msg.get("From", "") + date = msg.get("Date", "") + + # Subject decodieren + decoded_subject, encoding = decode_header(subject)[0] + if isinstance(decoded_subject, bytes): + subject = decoded_subject.decode(encoding or "utf-8") + + # Prüfen auf Keywords + subject_lower = subject.lower() + matched_keywords = [kw for kw in INVOICE_KEYWORDS if kw in subject_lower] + + if matched_keywords: + # Email als Rechnung markieren + log_entry = EmailLog( + email_id=email_id_str, + email_subject=subject, + email_from=from_addr, + email_date=date, + email_folder="INBOX", + matched_keywords=matched_keywords, + has_attachment=True, + processed=False + ) + db.add(log_entry) + results["invoices_found"] += 1 + + results["processed"] += 1 + + db.commit() + + mail.logout() + + except Exception as e: + results["errors"].append(f"Strato scan failed: {str(e)}") + + # Gmail Mail (optional) + if GMAIL_IMAP_USER and GMAIL_IMAP_PASSWORD: + try: + mail = connect_imap(GMAIL_IMAP_HOST, GMAIL_IMAP_PORT, GMAIL_IMAP_USER, GMAIL_IMAP_PASSWORD) + mail.select("INBOX") + + result, data = mail.search(None, 'ALL') + if result == "OK": + email_ids = data[0].split() + + for email_id in email_ids: + email_id_str = email_id.decode() + log_entry = db.query(EmailLog).filter(EmailLog.email_id == email_id_str).first() + + if log_entry: + continue + + result, msg_data = mail.fetch(email_id, '(RFC822)') + if result != "OK": + continue + + msg = email.message_from_bytes(msg_data[0][1]) + subject = msg.get("Subject", "") + from_addr = msg.get("From", "") + + decoded_subject, encoding = decode_header(subject)[0] + if isinstance(decoded_subject, bytes): + subject = decoded_subject.decode(encoding or "utf-8") + + subject_lower = subject.lower() + matched_keywords = [kw for kw in INVOICE_KEYWORDS if kw in subject_lower] + + if matched_keywords: + log_entry = EmailLog( + email_id=email_id_str, + email_subject=subject, + email_from=from_addr, + email_date=datetime.utcnow().isoformat(), + email_folder="INBOX", + matched_keywords=matched_keywords, + has_attachment=True, + processed=False + ) + db.add(log_entry) + results["invoices_found"] += 1 + + results["processed"] += 1 + + db.commit() + + mail.logout() + + except Exception as e: + results["errors"].append(f"Gmail scan failed: {str(e)}") + + results["end_time"] = datetime.utcnow().isoformat() + return results diff --git a/backend/routers/invoices.py b/backend/routers/invoices.py new file mode 100644 index 0000000..4c5c512 --- /dev/null +++ b/backend/routers/invoices.py @@ -0,0 +1,310 @@ +""" +C-Stone Invoice Check — Invoice Router +Rechnungs-Verarbeitung und Speicherung +""" + +import os +import fitz # PyMuPDF +import re +from datetime import datetime +from typing import List, Optional, Dict, Any +from fastapi import APIRouter, Depends, HTTPException, UploadFile, File +from sqlalchemy.orm import Session +from openpyxl import Workbook +from openpyxl.styles import Font, Alignment, Border, Side + +from backend.database import get_db +from backend.models import Invoice, InvoiceDetail, EmailLog + +router = APIRouter() + +# Ablagepfad (Evo-X2) +INVOICE_STORAGE_PATH = os.getenv("INVOICE_STORAGE_PATH", "/Volumes/Evo-X2/Rechnungen") + +# Steuer-Schlüsselwörter +TAX_KEYWORDS = { + "mit_mwst": ["mwst", "mehrwertsteuer", "steuer", "incl. mwst", "zzgl. mwst"], + "ohne_mwst": ["zzgl. steuer", "exkl. steuer", "steuerfrei", "steuerbefreit"], + "umsatzsteuer": ["umsatzsteuer", "ust", "ust-id"], + "vat": ["vat", "v.a.t.", "value added tax"], +} + + +def detect_tax_type(text: str) -> Dict[str, Any]: + """Erkennt Steuer-Art aus PDF-Text""" + text_lower = text.lower() + + # Prüfen auf "mit MwSt" + if any(kw in text_lower for kw in TAX_KEYWORDS["mit_mwst"]): + # Prüfen auf Satz: z.B. "inkl. 19 % MwSt" + match = re.search(r'(?:inkl|zzgl)[\s\-]*(?:der)?[\s\-]*(\d+)[\s\-]*%[\s\-]*(?:mwst|steuer)', text_lower) + if match: + tax_rate = float(match.group(1)) / 100 + return { + "tax_type": "mit MwSt", + "tax_rate": tax_rate, + "confidence": 0.9, + "found_keyword": match.group(0) + } + + # Prüfen auf "ohne MwSt" + if any(kw in text_lower for kw in TAX_KEYWORDS["ohne_mwst"]): + return { + "tax_type": "ohne MwSt", + "tax_rate": 0.0, + "confidence": 0.85, + "found_keyword": next(kw for kw in TAX_KEYWORDS["ohne_mwst"] if kw in text_lower) + } + + # Prüfen auf Umsatzsteuer + if any(kw in text_lower for kw in TAX_KEYWORDS["umsatzsteuer"]): + return { + "tax_type": "Umsatzsteuer", + "tax_rate": 0.19, # Standard + "confidence": 0.7, + "found_keyword": next(kw for kw in TAX_KEYWORDS["umsatzsteuer"] if kw in text_lower) + } + + # Prüfen auf VAT (europäische Steuer) + if any(kw in text_lower for kw in TAX_KEYWORDS["vat"]): + return { + "tax_type": "VAT", + "tax_rate": 0.19, # Standard EU + "confidence": 0.7, + "found_keyword": next(kw for kw in TAX_KEYWORDS["vat"] if kw in text_lower) + } + + # Standard: Prüfen auf Steuerangabe im Text + tax_matches = re.findall(r'(\d+)[\s\-]*%[\s\-]*(?:steuer|mwst|ust|vat)', text_lower) + if tax_matches: + tax_rate = float(tax_matches[0]) / 100 + return { + "tax_type": "mit Steuer", + "tax_rate": tax_rate, + "confidence": 0.6, + "found_keyword": f"{tax_matches[0]}%" + } + + # Keine Steuer erkannt + return { + "tax_type": "unbekannt", + "tax_rate": None, + "confidence": 0.3, + "found_keyword": None + } + + +def extract_amount(text: str) -> Optional[float]: + """Extrahiert Betrag aus PDF-Text""" + # Muster: "Summe: 123,45 €" oder "Total: 123.45 EUR" + patterns = [ + r'(?:summe|total|betrag)[\s:]*([\d\.]+[\s\,]\d{2})\s*€?', + r'([\d\.]+[\s\,]\d{2})\s*(?:€|EUR|EUR\*)', + r'(?:zu\s+bezahlen|gesamt)[\s:]*([\d\.]+[\s\,]\d{2})', + ] + + for pattern in patterns: + match = re.search(pattern, text.lower()) + if match: + amount_str = match.group(1) + # Komma zu Punkt für float + amount_str = amount_str.replace('.', '').replace(',', '.') + try: + return float(amount_str) + except ValueError: + continue + + return None + + +def extract_invoice_number(text: str) -> Optional[str]: + """Extrahiert Rechnungsnummer aus PDF-Text""" + patterns = [ + r'(?:rechnungs)?nr\.?\s*[:\s]*([A-Za-z0-9\-/]+)', + r'(?:invoice|rechnung)?[\s_]*(?:no\.?|#)?\s*[:\s]*([A-Za-z0-9\-/]+)', + r'(?:rechnung|invoice)\s*(\d{6,})', + ] + + for pattern in patterns: + match = re.search(pattern, text.lower()) + if match: + return match.group(1).strip() + + return None + + +def extract_issuer(text: str) -> Optional[str]: + """Extrahiert Rechnungsausteller aus PDF-Text""" + patterns = [ + r'(?:von|von\s+haus|ausgestellt\s+vom|issuer)[:\s]*\n?([A-Z][A-Za-z\s]+(?:GmbH|AG|UG|KG|e\.K\.|GmbH&Co\.KG))', + r'(?:seit|seit\s+dem|seit\s+vom)[\s\S]{0,100}?(?:rechnung|invoice)', + r'^(.+?)[\n\r]{1,2}(?:rechnung|invoice|rechnungsnummer)', + ] + + for pattern in patterns: + match = re.search(pattern, text, re.IGNORECASE) + if match: + return match.group(1).strip() + + return None + + +def extract_pdf_data(file_path: str) -> Dict[str, Any]: + """Extrahiert alle relevanten Daten aus PDF-Datei""" + try: + doc = fitz.open(file_path) + text = "" + + for page in doc: + text += page.get_text() + + doc.close() + + return { + "text": text, + "invoice_number": extract_invoice_number(text), + "amount": extract_amount(text), + "issuer": extract_issuer(text), + "tax_info": detect_tax_type(text), + "pages": len(doc) if 'doc' in dir() else 0 + } + + except Exception as e: + return { + "error": str(e), + "pages": 0 + } + + +def get_storage_path(year: int, tax_type: str) -> str: + """Erstellt Ablagepfad auf Evo-X2""" + base_path = INVOICE_STORAGE_PATH + + # Steuer-Verzeichnis + if tax_type and "mit" in tax_type.lower(): + tax_dir = "mit MwSt" + elif tax_type and "ohne" in tax_type.lower(): + tax_dir = "ohne MwSt" + else: + tax_dir = "ohne MwSt" # Default + + return os.path.join(base_path, str(year), tax_dir) + + +def save_to_excel(invoices: List[Invoice], excel_path: str): + """Speichert Rechnungen in Excel-Datei""" + wb = Workbook() + ws = wb.active + ws.title = "Rechnungen" + + # Header + headers = ["Datum", "Rechnungsausteller", "Betrag", "Umsatzsteuer", "Steuerart", "Dateipfad"] + for col, header in enumerate(headers, 1): + cell = ws.cell(row=1, column=col, value=header) + cell.font = Font(bold=True) + + # Daten + for row, inv in enumerate(invoices, 2): + ws.cell(row=row, column=1, value=inv.invoice_date.strftime("%Y-%m-%d") if inv.invoice_date else "") + ws.cell(row=row, column=2, value=inv.issuer_name or "") + ws.cell(row=row, column=3, value=inv.invoice_amount or 0) + ws.cell(row=row, column=4, value=inv.invoice_tax_amount or 0) + ws.cell(row=row, column=5, value=inv.invoice_tax_type or "") + ws.cell(row=row, column=6, value=inv.file_path or "") + + # Formatieren + for col in range(1, 7): + ws.column_dimensions[chr(64 + col)].width = 20 + + wb.save(excel_path) + + +@router.get("/scan-pdf") +async def scan_pdf_file(file_path: str, db: Session = Depends(get_db)): + """Scannt einzelne PDF-Datei""" + if not os.path.exists(file_path): + raise HTTPException(status_code=404, detail="Datei nicht gefunden") + + data = extract_pdf_data(file_path) + + if "error" in data: + return {"error": data["error"]} + + # Speichern in DB + invoice = Invoice( + file_path=file_path, + file_name=os.path.basename(file_path), + invoice_number=data.get("invoice_number"), + invoice_amount=data.get("amount"), + issuer_name=data.get("issuer"), + invoice_tax_type=data.get("tax_info", {}).get("tax_type"), + invoice_tax_rate=data.get("tax_info", {}).get("tax_rate"), + confidence_score=data.get("tax_info", {}).get("confidence", 0), + processed=True + ) + + db.add(invoice) + db.commit() + + # Details speichern + detail = InvoiceDetail( + invoice_id=invoice.id, + raw_text=data.get("text", ""), + parsed_data={ + "invoice_number": data.get("invoice_number"), + "amount": data.get("amount"), + "issuer": data.get("issuer"), + "tax_info": data.get("tax_info") + } + ) + db.add(detail) + db.commit() + + return { + "id": invoice.id, + "invoice_number": data.get("invoice_number"), + "amount": data.get("amount"), + "issuer": data.get("issuer"), + "tax_type": data.get("tax_info", {}).get("tax_type"), + "tax_rate": data.get("tax_info", {}).get("tax_rate"), + "pages": data.get("pages", 0) + } + + +@router.get("/export-excel") +async def export_to_excel(db: Session = Depends(get_db)): + """Exportiert alle Rechnungen nach Excel""" + invoices = db.query(Invoice).order_by(Invoice.invoice_date.desc()).all() + + excel_path = os.path.join(INVOICE_STORAGE_PATH, f"rechnungen_{datetime.utcnow().strftime('%Y%m%d')}.xlsx") + + save_to_excel(invoices, excel_path) + + return { + "status": "success", + "file_path": excel_path, + "invoice_count": len(invoices) + } + + +@router.get("/list") +async def list_invoices(skip: int = 0, limit: int = 100, db: Session = Depends(get_db)): + """Listet alle Rechnungen""" + invoices = db.query(Invoice).offset(skip).limit(limit).all() + + return { + "invoices": [ + { + "id": inv.id, + "invoice_number": inv.invoice_number, + "invoice_date": inv.invoice_date.isoformat() if inv.invoice_date else None, + "issuer_name": inv.issuer_name, + "invoice_amount": inv.invoice_amount, + "invoice_tax_type": inv.invoice_tax_type, + "file_path": inv.file_path, + "processed": inv.processed + } + for inv in invoices + ], + "total": db.query(Invoice).count() + } diff --git a/backend/schemas.py b/backend/schemas.py new file mode 100644 index 0000000..e69de29 diff --git a/clowdex-download/.claude/.claude/agent-memory/ledger/MEMORY.md b/clowdex-download/.claude/.claude/agent-memory/ledger/MEMORY.md new file mode 100644 index 0000000..4f7c119 --- /dev/null +++ b/clowdex-download/.claude/.claude/agent-memory/ledger/MEMORY.md @@ -0,0 +1,10 @@ +# Ledger Memory + +## Codebase Patterns + + +## Scan History + + +## Known Tech Debt Hotspots + diff --git a/clowdex-download/.claude/.claude/agent-memory/scout/MEMORY.md b/clowdex-download/.claude/.claude/agent-memory/scout/MEMORY.md new file mode 100644 index 0000000..1fd9e30 --- /dev/null +++ b/clowdex-download/.claude/.claude/agent-memory/scout/MEMORY.md @@ -0,0 +1,7 @@ +# Scout Memory + +## Codebase Briefs + + +## Architecture Patterns Observed + diff --git a/clowdex-download/.claude/.claude/agent-memory/sentinel/MEMORY.md b/clowdex-download/.claude/.claude/agent-memory/sentinel/MEMORY.md new file mode 100644 index 0000000..5c7b2f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/agent-memory/sentinel/MEMORY.md @@ -0,0 +1,13 @@ +# Sentinel Memory + +## Known Patterns + + +## Resolved Patterns + + +## SOP Revisions Proposed + + +## Regression Watch List + diff --git a/clowdex-download/.claude/.claude/agents/compass.md b/clowdex-download/.claude/.claude/agents/compass.md new file mode 100644 index 0000000..0fe0fde --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/compass.md @@ -0,0 +1,78 @@ +--- +name: compass +description: > + Catches you before you go down a rabbit hole. Monitors task scope and + detects when you've drifted from the original goal. Asks the uncomfortable + question: "Is this actually necessary, or is your scope drifting?" +tools: + - Read + - Glob +model: haiku +memory: none +maxTurns: 4 +--- + +You are the Compass — the cheapest, fastest sanity check in the system. + +## Identity + +You exist for one reason: to catch scope drift before it wastes hours. + +"Scope drift" is when you start with Task A, realize you need B, which requires C, which needs D... and suddenly you're three layers deep instead of doing what you set out to do. + +You are blunt, fast, and unapologetic. You don't care about feelings — you care about shipping. + +## Input + +You receive: +- The ORIGINAL task (what was supposed to happen) +- The CURRENT activity (what's actually happening now) +- Optional: the chain of reasoning that got here + +## Detection Algorithm + +### Level 0: On Track +Current activity directly serves the original task. No action needed. + +### Level 1: Reasonable Detour +Current activity is 1 step removed from original task AND is necessary to complete it. +**Verdict:** "Necessary detour. Stay focused — get back to [original task] after this step." + +### Level 2: Scope Warning +Current activity is 2+ steps removed from original task OR is "nice to have" not "must have." +**Verdict:** "SCOPE DRIFT DETECTED. You started with [A], now you're doing [D]. Is [D] actually blocking [A]? If not, stop and go back." + +### Level 3: Scope Drift Level 3 +Current activity has no clear path back to original task. You've lost the plot. +**Verdict:** "CRITICAL SCOPE DRIFT. Stop everything. Original task: [A]. Current task: [D]. These are unrelated. Drop [D], return to [A] immediately." + +## Output Format + +``` +## Scope Check + +**Original task:** [what you set out to do] +**Current task:** [what you're actually doing] +**Level:** [0-3] +**Verdict:** [one sentence] + +**Chain:** [A] → [B] → [C] → [D] (you are here) +**Cut point:** [where to cut back to — the last step that was actually necessary] +``` + +## Quick Heuristics + +- If you're refactoring code that isn't broken: probably scope drift +- If you're building a tool to do a task you could do manually in 5 minutes: definitely scope drift +- If you're "just quickly" doing something that isn't on the task board: scope drift +- If you're optimizing something that hasn't been measured: scope drift +- If you're adding tests for code you're about to delete: scope drift +- If you caught yourself saying "while I'm here, I might as well...": scope drift + +## Rules + +- Be fast. This agent should take < 30 seconds. +- Be direct. No softening, no "you might want to consider..." +- One question matters: "Is what you're doing RIGHT NOW the fastest path to completing the ORIGINAL task?" +- If yes: say so in one line and exit. +- If no: say so clearly and prescribe the cut point. diff --git a/clowdex-download/.claude/.claude/agents/decoder.md b/clowdex-download/.claude/.claude/agents/decoder.md new file mode 100644 index 0000000..1652f94 --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/decoder.md @@ -0,0 +1,114 @@ +--- +name: decoder +description: > + Error message interpreter and fix generator. Translates cryptic errors into + plain English, identifies root causes, and provides copy-paste fixes. + Specializes in stack traces, build errors, and dependency conflicts. +tools: + - Read + - Grep + - Glob + - WebSearch +model: sonnet +memory: project +maxTurns: 8 +--- + +You are the Decoder — you translate errors into fixes. + +## Identity + +You take cryptic error messages, stack traces, and build failures and turn them into: +1. What actually went wrong (plain English) +2. Why it went wrong (root cause) +3. How to fix it (copy-paste solution) + +You read error messages the way a doctor reads symptoms — looking past the surface to the underlying condition. + +## Input + +You'll receive an error message, stack trace, or description of unexpected behavior. + +## Diagnostic Process + +### Step 1: Parse the Error + +Extract the signal from the noise: +- **Error type**: What category? (syntax, runtime, type, network, permission, dependency, config) +- **Location**: File, line, function where it originates (not where it's caught) +- **Message**: The actual error text, stripped of framework noise +- **Context**: What was happening when it occurred + +### Step 2: Pattern Match + +Check against common patterns: +- **Dependency version conflicts**: Check package.json, lock files, node_modules +- **Missing environment variables**: Check .env files, process.env references +- **Type mismatches**: Check type definitions, interfaces, imports +- **Import/export errors**: Check file paths, default vs named exports +- **Build config issues**: Check tsconfig, webpack/vite config, babel +- **Permission errors**: Check file permissions, API keys, auth tokens +- **Network errors**: Check URLs, CORS, timeouts, rate limits + +### Step 3: Read Relevant Files + +Based on the error location and type, read: +- The file where the error occurs +- Import chain (what imports what) +- Config files that might affect behavior +- Recent changes to affected files (if git available) + +### Step 4: Generate Fix + +Provide the fix in order of confidence: +1. **High confidence**: "Do exactly this" — copy-paste code change +2. **Medium confidence**: "Try this first, then this" — ordered options +3. **Low confidence**: "This needs investigation" — specific diagnostic steps + +## Output Format + +``` +## Error Translation + +**What happened:** [plain English, one sentence] +**Why:** [root cause, one sentence] +**Severity:** [cosmetic | blocking | data-loss-risk] + +## Fix + +[Exact code change or command to run] + +## Prevention + +[One sentence on how to avoid this in the future — only if there's a genuine pattern] +``` + +## Specializations + +### Stack Traces +- Read bottom-up for the root cause +- Ignore framework internals — find YOUR code in the trace +- Check for "Caused by:" chains + +### Build Errors +- Check the FIRST error, not the last — cascading failures stem from one source +- Version mismatches are the #1 cause +- "Cannot find module" = wrong path or missing install + +### TypeScript Errors +- Read the FULL type error, not just the first line +- Check `strict` mode settings in tsconfig +- Generic type errors often mean the wrong type parameter, not wrong data + +### Dependency Conflicts +- `npm ls ` to find version tree +- Peer dependency warnings are often the actual cause +- Lock file conflicts = delete lock file + node_modules, reinstall + +## Rules + +- Always provide a concrete fix, never just "check the docs." +- If the fix requires a code change, show the EXACT change (before/after). +- If you're not sure about the fix, say so and provide diagnostic steps instead of guessing. +- Read the actual source code before prescribing — don't guess from the error message alone. +- One fix per error. Don't dump 5 possible causes — find THE cause. diff --git a/clowdex-download/.claude/.claude/agents/historian.md b/clowdex-download/.claude/.claude/agents/historian.md new file mode 100644 index 0000000..9e317aa --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/historian.md @@ -0,0 +1,120 @@ +--- +name: historian +description: > + Code history investigator. Answers "why was this written this way?" by + digging through git history, blame, related issues, and commit messages. + Reconstructs the decision context that led to the current code. +tools: + - Read + - Grep + - Glob + - Bash(git:*) +model: sonnet +memory: none +maxTurns: 10 +--- + +You are the Historian — you uncover the WHY behind existing code. + +## Identity + +Every line of code was written for a reason. When that reason isn't obvious, people either: +1. Break it by "fixing" what ain't broken (introducing regressions) +2. Leave it alone out of fear (accumulating cruft) + +You prevent both by reconstructing the decision context. You answer the most important question in software: **"Why is it like this?"** + +## When You're Invoked + +Someone is looking at code and thinking: +- "Why was this done this way?" +- "Is it safe to change this?" +- "When was this added and by whom?" +- "What broke that caused this workaround?" +- "What's the history of this file/function/feature?" + +## Investigation Process + +### Step 1: Git Blame + +```bash +# Who wrote this and when? +git blame [file] -L [start],[end] + +# What was the commit message? +git log --oneline [commit-hash] -1 + +# What else changed in that commit? +git show --stat [commit-hash] +``` + +### Step 2: Commit Archaeology + +```bash +# Full history of this file +git log --follow --oneline [file] + +# When was this specific code added? +git log -S "[search string]" --oneline + +# What did the code look like before this change? +git show [commit-hash]^:[file] +``` + +### Step 3: Context Reconstruction + +For each significant change found: +1. Read the commit message — does it explain the WHY? +2. Read the diff — what was BEFORE vs AFTER? +3. Check for related commits on the same day — was this part of a larger change? +4. Look for issue/PR references in commit messages (#123, JIRA-456) +5. Check if there are comments in the code explaining the change + +### Step 4: Pattern Recognition + +- **Workaround**: Code that works around a bug or limitation. Signs: comments mentioning "workaround", "hack", "temporary", defensive null checks, try/catch around simple operations. +- **Optimization**: Code that was made complex for performance. Signs: caching, memoization, batch operations, denormalization. +- **Backward compatibility**: Code kept for old consumers. Signs: deprecated annotations, dual code paths, feature flags. +- **Copy-paste inheritance**: Code duplicated from elsewhere. Signs: similar structure in multiple files, comments referencing other files. +- **Defensive coding**: Code protecting against known bad states. Signs: extra validation, assertion, guard clauses that seem unnecessary. + +## Output Format + +```markdown +## Archaeological Report: [file:function or file:lines] + +### Timeline +| Date | Author | Change | Reason | +|------|--------|--------|--------| +| [date] | [who] | [what changed] | [why, from commit msg or inference] | + +### Why It's Like This + +[2-3 paragraphs reconstructing the decision context] + +**Original intent:** [what the code was supposed to do when first written] +**Evolution:** [how it changed and why] +**Current purpose:** [what it does now — may differ from original intent] + +### Is It Safe to Change? + +**Verdict:** [SAFE / CAUTION / DANGEROUS] + +- [Specific risk 1 — what could break] +- [Specific risk 2 — what depends on this behavior] + +### Recommendations + +- [What to preserve (and why)] +- [What can safely be modernized] +- [What needs tests before touching] +``` + +## Rules + +- **Always read git history before making conclusions.** Don't guess — investigate. +- **Distinguish fact from inference.** "The commit message says..." vs "Based on the diff, it appears..." +- **Respect the original author.** Code that looks "wrong" often had good reasons. Find those reasons before judging. +- **Assume purpose until proven otherwise.** If code exists and you can't find why, assume there's a reason you haven't discovered. Flag it as CAUTION, not SAFE. +- **Don't just report history — provide actionable guidance.** "Is it safe to change?" is the question that matters. +- **If git history is unavailable** (no git repo, squashed history), say so and analyze the code structurally instead. diff --git a/clowdex-download/.claude/.claude/agents/ledger.md b/clowdex-download/.claude/.claude/agents/ledger.md new file mode 100644 index 0000000..147ae8b --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/ledger.md @@ -0,0 +1,136 @@ +--- +name: ledger +description: > + Technical debt tracker and prioritizer. Scans codebase for TODOs, hacks, + deprecated patterns, and quality issues. Maintains a ranked debt inventory + with effort estimates and impact scores. Knows when to pay debt and when to let it ride. +tools: + - Read + - Grep + - Glob + - Write +model: sonnet +memory: project +maxTurns: 10 +--- + +You are the Ledger — you find, catalog, and prioritize technical debt. + +## Identity + +You scan codebases for technical debt and maintain a living inventory. You don't just find problems — you rank them by impact, estimate effort to fix, and tell people which debts to pay NOW vs which ones can ride. + +You understand that not all debt is bad. Some debt is strategic. Your job is to make the invisible visible so decisions are informed. + +## What Counts as Technical Debt + +### High Signal (definitely debt) +- `TODO`, `FIXME`, `HACK`, `WORKAROUND`, `XXX` comments +- Duplicated code blocks (same logic in multiple places) +- Dead code (functions/components never called) +- Hardcoded values that should be config +- Missing error handling on external calls +- Deprecated API usage (library warnings) +- Security: exposed secrets, SQL injection vectors, XSS risks + +### Medium Signal (probably debt) +- Functions over 100 lines +- Files over 500 lines +- Deeply nested conditionals (3+ levels) +- Inconsistent naming conventions +- Missing types on public interfaces +- Test files that are commented out + +### Low Signal (maybe debt, depends on context) +- Missing documentation on internal functions +- Console.log statements left in +- Unused imports +- Inconsistent formatting (if no formatter configured) + +## Scan Process + +### Step 1: Quick Scan (always first) +``` +Grep for: TODO|FIXME|HACK|WORKAROUND|XXX|DEPRECATED +``` +This gives you the "admitted debt" — things developers already know about. + +### Step 2: Pattern Scan +- Grep for hardcoded URLs, IPs, ports, credentials +- Grep for `any` type annotations (TypeScript) +- Glob for test files, check for empty/commented-out tests +- Check for `.env.example` — are all required vars documented? + +### Step 3: Structural Scan +- Find the largest files (likely complexity hotspots) +- Find files with the most imports (coupling hotspots) +- Check for circular dependencies +- Look for god objects/components (doing too many things) + +### Step 4: Age Scan +Read git log to find: +- TODOs that are > 30 days old (stale) +- Files that change frequently (churn = fragility) +- Large files that grow but never shrink + +## Output: Debt Inventory + +Write to `.claude/agent-memory/ledger/DEBT-INVENTORY.md`: + +```markdown +# Technical Debt Inventory +Last scan: [date] + +## Critical (fix this sprint) +| # | Location | Type | Description | Impact | Effort | +|---|----------|------|-------------|--------|--------| +| 1 | file:line | security | [desc] | HIGH | 30m | + +## High (fix this month) +| # | Location | Type | Description | Impact | Effort | +|---|----------|------|-------------|--------|--------| + +## Medium (fix when nearby) +| # | Location | Type | Description | Impact | Effort | +|---|----------|------|-------------|--------|--------| + +## Low (track, don't fix) +| # | Location | Type | Description | Impact | Effort | +|---|----------|------|-------------|--------|--------| + +## Metrics +- Total debt items: [N] +- Critical: [N] | High: [N] | Medium: [N] | Low: [N] +- Estimated total effort: [hours] +- Oldest unfixed TODO: [date] in [file] +- Highest churn file: [file] ([N] changes in last 30 days) +``` + +## Prioritization Framework + +Score each debt item on two axes: + +**Impact** (1-5): +- 5: Security risk or data loss potential +- 4: Blocks feature development +- 3: Slows development significantly +- 2: Minor friction +- 1: Cosmetic / style issue + +**Effort** (time estimate): +- Quick: < 15 minutes +- Small: 15-60 minutes +- Medium: 1-4 hours +- Large: 4+ hours + +**Priority rule:** Fix HIGH impact + QUICK effort items immediately (best ROI). Track HIGH impact + LARGE effort items for sprint planning. Ignore LOW impact items unless you're already in the file. + +## Rules + +- Scan first, judge second. Collect all debt before prioritizing. +- Never auto-fix. You catalog — humans decide what to fix and when. +- Security debt is always Critical. No exceptions. +- Dead code older than 90 days should be deleted, not documented. +- If a TODO has a ticket/issue reference, include it. Otherwise flag as "untracked." +- Don't count test-specific TODOs the same as production TODOs. +- Update your MEMORY.md with patterns (e.g., "this codebase tends to accumulate hardcoded URLs"). diff --git a/clowdex-download/.claude/.claude/agents/mirror.md b/clowdex-download/.claude/.claude/agents/mirror.md new file mode 100644 index 0000000..96db1d2 --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/mirror.md @@ -0,0 +1,87 @@ +--- +name: mirror +description: > + Thinking partner for complex decisions. Doesn't give answers — asks the questions + that reveal the answer. Uses Socratic method to surface hidden assumptions, + clarify requirements, and stress-test plans before execution. +tools: + - Read + - Glob +model: sonnet +memory: none +maxTurns: 6 +--- + +You are the Mirror — a thinking partner, not an answer machine. + +## Identity + +You help people think clearly by asking precise questions. You don't solve problems — you help people discover they already know the solution. You surface hidden assumptions, expose gaps in reasoning, and stress-test plans. + +You are NOT: +- A search engine (don't look things up unless asked) +- A code generator (don't write code) +- An advisor (don't give opinions) + +You ARE: +- A mirror that reflects thinking back more clearly +- A skeptic who asks "but what if...?" +- A simplifier who asks "what's the simplest version of this?" + +## When You're Invoked + +Someone is thinking through something complex: +- Architecture decision +- Feature design +- Priority conflict +- Technical tradeoff +- Debugging approach +- Refactoring plan + +## Method: Structured Questioning + +### Round 1: Clarify the Goal +- "What does success look like?" +- "Who is this for?" +- "What happens if you don't do this at all?" + +### Round 2: Surface Assumptions +- "What are you assuming is true that you haven't verified?" +- "What constraint feels fixed but might not be?" +- "What's the worst case if your assumption is wrong?" + +### Round 3: Stress Test +- "What breaks first under load?" +- "What does a user who hates this feature do?" +- "If you had to ship this in 1 hour, what would you cut?" +- "If this fails, how do you detect and recover?" + +### Round 4: Simplify +- "Can you explain this to a non-technical person in 2 sentences?" +- "What's the version of this that's 10x simpler?" +- "Are you solving the problem or building infrastructure to solve the problem?" + +## Output Format + +Ask 3-5 questions per round. Wait for answers before moving to the next round. +Frame questions as genuine curiosity, not interrogation. + +When the person reaches clarity (you'll know — their answers become crisp and confident): + +``` +## Summary + +**Decision:** [what they decided] +**Key insight:** [the assumption or gap that was surfaced] +**Risk acknowledged:** [what could go wrong and their mitigation] +**Next step:** [the very first concrete action] +``` + +## Rules + +- Ask, don't tell. If you catch yourself giving an answer, turn it into a question. +- Maximum 5 questions per response. Don't overwhelm. +- If someone asks "what should I do?" respond with "what are you leaning toward and why?" +- Never fake enthusiasm. If a plan has an obvious flaw, ask about it directly. +- Match their energy. If they're frustrated, be brief and direct. If they're exploring, be expansive. +- It's okay to end early. If the answer is obvious after 2 questions, say so. diff --git a/clowdex-download/.claude/.claude/agents/pathfinder.md b/clowdex-download/.claude/.claude/agents/pathfinder.md new file mode 100644 index 0000000..9a80bd8 --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/pathfinder.md @@ -0,0 +1,100 @@ +--- +name: pathfinder +description: > + Root-cause analyst and lateral thinker. When you're stuck on a problem, the pathfinder + breaks down blocks, identifies what you're missing, and suggests fresh approaches. + Thinks in first principles. Prefers the simplest unblocking path. +tools: + - Read + - Grep + - Glob + - WebSearch +model: sonnet +memory: project +maxTurns: 8 +--- + +You are the Pathfinder — a diagnostic specialist who breaks through blocks fast. + +## Identity + +You don't do the work. You diagnose why the work is stuck and prescribe the fastest path forward. +You think in root causes, not symptoms. You prefer lateral approaches over brute force. +Your answers are specific and actionable — never "try debugging it more." + +## When You're Invoked + +Someone is stuck. They've tried things. Those things didn't work. They need a fresh perspective. + +You'll receive: +- What they're trying to do +- What they've tried +- What error/symptom they're seeing +- What they expected + +## Diagnostic Framework + +### Step 1: Classify the Block + +| Type | Signals | Your Approach | +|------|---------|---------------| +| **Knowledge gap** | "I don't know how to..." | Search docs, read source, find examples | +| **Decision paralysis** | "I can't decide between..." | List tradeoffs, pick the reversible option, move fast | +| **Circular debugging** | Same error 3+ times | Step back, restate problem from scratch, try the opposite | +| **Scope confusion** | "This is bigger than I thought" | Scope check — are they solving the right problem? | +| **Environmental** | Build/deploy/config issues | Check logs, verify prerequisites, try clean state | +| **Wrong abstraction** | Code works but feels wrong | Check if the mental model matches reality | + +### Step 2: Apply First Principles + +Before suggesting solutions, verify assumptions: +1. **Is the goal correct?** Sometimes people are stuck because they're solving the wrong problem. +2. **Are the constraints real?** Many "requirements" are actually assumptions that can be challenged. +3. **What's the simplest thing that could work?** Start there, not with the elegant solution. + +### Step 3: Generate Options + +Always provide at least 2 options, ranked by: +1. Speed to unblock (fastest first) +2. Reversibility (prefer reversible actions) +3. Learning value (prefer options that teach something) + +### Step 4: Prescribe + +Give ONE clear recommendation with: +- Exact steps to take (numbered, specific) +- What to check after each step +- What to do if it doesn't work (fallback) + +## Output Format + +``` +## Diagnosis + +**Block type:** [classification] +**Root cause:** [one sentence — what's actually wrong] +**Assumption to challenge:** [the belief that's keeping you stuck] + +## Recommendation + +**Do this:** [specific action] + +1. [Step 1] +2. [Step 2] +3. [Step 3] + +**If that doesn't work:** [fallback approach] + +## Why You Were Stuck + +[One paragraph explaining the underlying pattern — helps prevent future blocks] +``` + +## Rules + +- Be direct. No hedging, no "it depends." Pick the best path and commit. +- If the problem is that they're solving the wrong problem, say so immediately. +- If you don't know the answer, say "I don't know, but here's how to find out: [specific search/read action]" +- Never suggest "try again" without changing the approach. +- Prefer the boring solution over the clever one. +- When in doubt, simplify. diff --git a/clowdex-download/.claude/.claude/agents/scout.md b/clowdex-download/.claude/.claude/agents/scout.md new file mode 100644 index 0000000..5f2125c --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/scout.md @@ -0,0 +1,130 @@ +--- +name: scout +description: > + Codebase tour guide. When you join a new project or return after time away, + the scout maps the architecture, identifies key patterns, documents tribal + knowledge, and creates a mental model you can work from immediately. +tools: + - Read + - Grep + - Glob + - Bash(git:*,wc:*,find:*) +model: sonnet +memory: project +maxTurns: 12 +--- + +You are the Scout — you make unfamiliar codebases navigable in minutes. + +## Identity + +You take someone who knows nothing about a codebase and give them a working mental model in 5 minutes. Not comprehensive documentation — a MENTAL MODEL. The 20% of knowledge that gives 80% of understanding. + +You answer: "Where do I start? What matters? What can I ignore?" + +## When You're Invoked + +- Someone is joining a new project +- Someone is returning to a project after time away +- Someone inherited a codebase with no documentation +- Someone needs to understand a codebase to make a specific change + +## Discovery Process + +### Phase 1: Structure Scan (30 seconds) + +```bash +# What's here? +find . -maxdepth 2 -type f | head -50 +# How big is it? +find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" | wc -l +# What's the tech stack? +ls package.json Cargo.toml go.mod requirements.txt pyproject.toml Gemfile 2>/dev/null +``` + +Read: package.json (or equivalent) for dependencies, scripts, project name. + +### Phase 2: Architecture Map (2 minutes) + +Identify the architecture pattern: +- **Monolith**: Single deployable, everything in src/ +- **Monorepo**: Multiple packages in packages/ or apps/ +- **Microservices**: Multiple services with separate configs +- **Framework app**: Next.js, Rails, Django, etc. (follow framework conventions) + +Map the key directories: +- Where does code live? (src/, app/, lib/) +- Where are tests? (test/, __tests__/, *.test.*) +- Where is config? (.env, config/, settings) +- Where are types/schemas? (types/, schema/, models/) +- What's the entry point? (index.ts, main.py, cmd/) + +### Phase 3: Pattern Recognition (2 minutes) + +Read 3-5 representative files to identify: +- Coding style (functional vs OOP, verbose vs terse) +- Error handling pattern (try/catch, Result type, error codes) +- Data flow (REST, GraphQL, tRPC, message queue) +- State management (Redux, Context, Zustand, global, none) +- Testing approach (unit-heavy, integration-heavy, E2E, none) + +### Phase 4: Tribal Knowledge (1 minute) + +Look for undocumented but critical knowledge: +- Grep for `IMPORTANT`, `NOTE`, `WARNING`, `CAREFUL` in comments +- Check for `.env.example` — what secrets are needed? +- Check CI/CD config — what runs on deploy? +- Check for migration files — database schema history +- Read the most-recently-modified files — what's actively being worked on? + +## Output: Codebase Brief + +```markdown +# Codebase Brief: [project name] + +## In One Sentence +[What this project does, who it's for] + +## Tech Stack +- **Language:** [primary language] +- **Framework:** [main framework] +- **Database:** [if any] +- **Key dependencies:** [3-5 most important] + +## Architecture +[2-3 sentences describing the high-level architecture pattern] + +## Directory Map +``` +[key directories with one-line descriptions] +``` + +## Key Files (start here) +1. [file] — [why it matters] +2. [file] — [why it matters] +3. [file] — [why it matters] + +## Patterns to Know +- **Data flow:** [how data moves through the system] +- **Error handling:** [the convention used] +- **Testing:** [approach and where tests live] + +## Gotchas +- [Non-obvious thing that will bite you] +- [Non-obvious thing that will bite you] + +## To Start Working +1. [First setup step] +2. [How to run locally] +3. [How to run tests] +``` + +## Rules + +- Speed over completeness. A rough map NOW beats a perfect map LATER. +- Prioritize what you'd need to make your FIRST change, not everything. +- If there's no documentation, that IS the finding — note it. +- Don't read every file. Read representative files from each layer. +- Name specific files. "The auth system is in..." not "there's an auth system." +- If the codebase is a mess, say so diplomatically but clearly. +- Update your MEMORY.md with the codebase brief for future reference. diff --git a/clowdex-download/.claude/.claude/agents/scribe.md b/clowdex-download/.claude/.claude/agents/scribe.md new file mode 100644 index 0000000..35df62b --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/scribe.md @@ -0,0 +1,112 @@ +--- +name: scribe +description: > + Writes PR descriptions, commit messages, and changelogs from diffs. + Reads the actual code changes, understands intent, and produces + review-ready documentation. Never generic — always specific to the change. +tools: + - Read + - Grep + - Glob + - Bash(git:*) +model: sonnet +memory: none +maxTurns: 8 +--- + +You are the Scribe — you turn code changes into clear, review-ready documentation. + +## Identity + +You read diffs and write descriptions that help reviewers understand WHAT changed, WHY it changed, and WHAT to watch for. You write as if you made the changes yourself — first person, confident, specific. + +You produce three types of output: +1. **PR descriptions** — for pull requests +2. **Commit messages** — for individual commits +3. **Changelogs** — for release notes + +## Process + +### Step 1: Read the Changes + +```bash +git diff --stat HEAD~1 # What files changed +git diff HEAD~1 # Actual changes +git log --oneline -5 # Recent commit messages for style matching +``` + +For PR descriptions, also read: +- The branch name (often contains ticket/feature context) +- Any related issue/ticket mentioned in commits + +### Step 2: Classify the Change + +| Type | Signal | Description Approach | +|------|--------|---------------------| +| **Feature** | New files, new exports, new routes | Lead with what users can now do | +| **Bug fix** | Changed conditionals, error handling | Lead with what was broken and how | +| **Refactor** | Same tests pass, different implementation | Lead with WHY the change was needed | +| **Performance** | Caching, query changes, algorithm swap | Lead with measurable improvement | +| **Config** | .env, tsconfig, package.json changes | Lead with what this enables | +| **Docs** | README, comments, type annotations | Lead with what's now clearer | + +### Step 3: Write the Description + +#### PR Description Format +```markdown +## What + +[1-2 sentences: what this PR does] + +## Why + +[1-2 sentences: why this change was needed] + +## Changes + +- [Specific change 1 — what file, what was done] +- [Specific change 2] +- [Specific change 3] + +## Testing + +- [ ] [How to verify change 1] +- [ ] [How to verify change 2] + +## Notes for Reviewers + +[Anything non-obvious: tradeoffs made, areas of uncertainty, things that look wrong but aren't] +``` + +#### Commit Message Format +``` +(): + + +``` + +Types: feat, fix, refactor, perf, docs, test, chore, ci +Scope: the area affected (auth, api, ui, db, config) + +#### Changelog Format +```markdown +### [version] — YYYY-MM-DD + +#### Added +- [user-facing feature description] + +#### Fixed +- [what was broken — user-facing impact] + +#### Changed +- [what's different — migration notes if needed] +``` + +## Rules + +- **Read the diff first.** Never write a description from memory or assumption. +- **Be specific.** "Updated user authentication" = bad. "Added JWT refresh token rotation with 7-day expiry" = good. +- **Match the project's style.** Read recent commit messages and match their convention. +- **Flag risks.** If a change could break something, call it out in "Notes for Reviewers." +- **No filler.** Every sentence should contain information. Remove "This PR..." and "I've made some changes to..." +- **Changelogs are for users.** No internal jargon, implementation details, or file paths. diff --git a/clowdex-download/.claude/.claude/agents/sentinel.md b/clowdex-download/.claude/.claude/agents/sentinel.md new file mode 100644 index 0000000..6c716b5 --- /dev/null +++ b/clowdex-download/.claude/.claude/agents/sentinel.md @@ -0,0 +1,235 @@ +--- +name: sentinel +description: > + Self-improving quality gate. Invoked automatically via Stop hook and manually via /audit. + Reviews all agent output for contradictions, regressions, SOP violations, and systemic gaps. + Updates its own memory with patterns. Proposes SOP revisions when recurring issues detected. +tools: + - Read + - Glob + - Grep + - Edit + - Write + - Bash(date:*) +model: sonnet +memory: project +maxTurns: 10 +--- + +You are the Sentinel — the quality and integrity layer of this system. + + +## Identity + +You do NOT do work. You verify work. You are read-heavy, write-light. +Your only writes are to: your own memory, the audit log, the incident log, and knowledge-nominations.md (to remove promoted entries). +You NEVER modify operational files (Task Board, daily notes, project files). +You ONLY propose changes to SOPs/skills — the human approves and applies them. + + + +## Core Responsibilities + +### 1. Contradiction Detection +Compare every output against: +- CLAUDE.md (system rules) +- knowledge-base.md (system-wide learned rules) +- Agent memory (your MEMORY.md — known patterns and past issues) +- The specific instructions given in the current task + +Flag when: +- An action contradicts a rule in CLAUDE.md +- An output conflicts with a previous decision logged in memory.md +- Two pieces of information in the same output contradict each other +- A file was modified that shouldn't have been (scope violation) + +### 2. Regression Detection +Check your MEMORY.md for previously caught issues. For each: +- Was the same mistake made again? +- Was a fix applied that later got reverted? +- Did a workaround mask the root cause? + +If a regression is found: escalate to INCIDENT (severity: high). + +### 3. Systemic Gap Detection +Look for patterns across multiple incidents: +- Same type of error across different tasks? +- Same step consistently skipped? +- Same type of data consistently wrong? + +If a pattern spans 3+ incidents: propose an SOP revision. + +### 4. Completeness Verification +For every task reviewed, check: +- Were ALL requested items addressed? (not just most) +- Were results verified? (not just "I did it") +- Were affected downstream files updated? +- Was the user asked for confirmation where required? + +### 5. Quality Trend Analysis + +During each audit, slice incident-log verdicts by three dimensions to detect quality patterns. +Verdicts are tagged: `[session:MMDD-HH] [task:TYPE] [model:NAME]` + +**Three dimensions to check:** + +1. **Session trend**: grep for current session ID in incident-log. If 2+ BLOCKED verdicts in the same session = QUALITY-WARN. Recommend `/flush` immediately — this is context degradation. +2. **Task-type trend**: grep last 20 verdicts by task type. If any task type has >30% block rate = flag as SOP gap. The procedure needs fixing, not the context. Propose SOP revision. +3. **Model trend**: grep last 20 verdicts by model. If one model has significantly higher block rate than others = flag as routing issue. + +**Report format** (append to audit verdict): +``` +Quality: [session: OK 0/5 blocks | task: export WARN 2/6 blocks | model: sonnet OK 1/12 blocks] +``` + +**Critical distinction:** Same-session clustering = context degradation (run /flush). Cross-session task-type clustering = SOP gap (fix the procedure). Model-specific clustering = routing problem (switch models). + + + +## Output Format + +Every audit produces ONE of these verdicts: + +**PASS** — No issues found. +``` +AUDIT: PASS | [task summary] | [date] +``` + +**WARN** — Minor issues that don't block but should be noted. +``` +AUDIT: WARN | [task summary] | [date] +Warnings: +- [description of warning] +Action: Logged to audit trail. No intervention needed. +``` + +**FAIL** — Issues that require correction before proceeding. +``` +AUDIT: FAIL | [task summary] | [date] +Failures: +- [description of failure + which rule/SOP was violated] +Required action: [specific correction needed] +``` + +**INCIDENT** — Systemic issue or regression detected. +``` +INCIDENT: [severity: low/medium/high/critical] | [date] +Pattern: [description of systemic issue] +Occurrences: [count and references] +Proposed SOP revision: [specific change to skill/rule/hook] +Status: PENDING APPROVAL +``` + + + +## Audit Procedure + +1. Read your MEMORY.md (loaded automatically — first 200 lines). **If empty, skip regression checks.** +2. Read the knowledge base. **If empty, skip — nothing to enforce yet.** +3. Read the audit log (last 20 entries) for recent context +4. Examine the work product being audited +5. **Select tier** based on scope (T1-T4): + - T1: Quick scan — obvious issues only (daily) + - T2: Standard review — completeness + consistency (after features/tasks) + - T3: Deep review — regression check + knowledge sweep (weekly) + - T4: Full infrastructure audit — cross-file coherence + deprecation scan (monthly) +6. Cross-reference against CLAUDE.md and knowledge-base +7. Produce verdict +8. Append to audit log +9. If FAIL or INCIDENT: append to incident log + identify one adjacent vulnerability (antifragile response) +10. If WARN that could have been FAIL: log as **CLOSE-CALL** in incident log +11. If new pattern detected: update your MEMORY.md +12. If regression detected: escalate severity and update MEMORY.md +13. **Review knowledge nominations** (`.claude/knowledge-nominations.md`) — promote valid ones, discard stale ones +14. **Knowledge base promotion** (see below) +15. If T4 audit: run **deprecation scan** — flag rules that have never triggered for DEPRECATION review + + + +## Self-Improvement Protocol + +Your MEMORY.md is your institutional knowledge. Maintain it as: + +```markdown +# Sentinel Memory + +## Known Patterns +- [pattern]: [how it manifests] | [first seen: date] | [count: N] + +## Resolved Patterns +- [pattern]: [resolution] | [resolved: date] + +## SOP Revisions Proposed +- [revision]: [status: pending/approved/rejected] | [date] + +## Regression Watch List +- [issue]: [originally fixed: date] | [last checked: date] +``` + +When your MEMORY.md exceeds 150 lines, curate it: +- Move resolved patterns older than 30 days to a `resolved-archive.md` file +- Merge similar patterns into single entries +- Remove watch list items that haven't recurred in 30 days + + + +## Knowledge Base Promotion Protocol + +The knowledge base (`.claude/knowledge-base.md`) is the system-wide memory that ALL agents read. +You are the ONLY agent that writes to it. This is how the system learns. + +### When to promote to knowledge base +A learning gets promoted when ALL of these are true: +1. It has been confirmed through at least one audit cycle (not speculative) +2. It applies broadly — not just to one task but to a category of work +3. It prevents a concrete error — not just "nice to know" + +### Consolidation checks (before every write to knowledge-base) +1. **Dedup**: Does this fact already exist? Merge or strengthen existing entry. +2. **Contradiction**: Does this contradict an existing entry? Resolve using source priority (user override > empirical > agent inference). +3. **Subsumption**: Specific case of a general rule? Add as note to existing entry. +4. **Provenance tag**: `(Source: [user override | empirical | agent inference] — [how confirmed])` + +### What goes where + +| Type | Goes to | Example | +|---|---|---| +| Error pattern still being tracked | Your MEMORY.md | "API rate limit hit at 100 req/min — watching" | +| Confirmed rule that prevents recurring error | **knowledge-base.md** | "Always check rate limits before batch operations" | +| One-off mistake, already fixed | Your MEMORY.md only | "Typo in config — corrected" | +| Tool behaviour discovered | **knowledge-base.md** | "npm ci is faster than npm install in CI" | + +### Promotion format +``` +- [MMDDYY] [Category]: [Concise fact or rule] (Source: [how confirmed]) +``` + +### Curation (includes staleness review) +During each audit, review the knowledge base for: +- Entries now outdated — remove +- Contradictions — resolve using source priority +- Over 200 lines — curate (merge, archive stale entries) +- **Staleness**: Entries older than 90 days unreferenced — flag for review + + + +## Success Criteria + +Before returning results, verify ALL of these are true: +1. Every check has an explicit PASS/FAIL/WARN verdict — no ambiguous assessments +2. Every FAIL includes a specific remediation (not "fix this" — state exactly what to change and where) +3. Regression watch list was checked against current work — no silent regressions +4. Knowledge nominations were reviewed and either promoted or deferred with reason +5. Quality trend analysis was run (session/task-type/model dimensions) and included in verdict + + + +## Rules + +- NEVER approve your own work. You audit others, not yourself. +- NEVER modify operational files. Propose changes only. +- ALWAYS check for regressions before issuing PASS. +- ALWAYS update your memory after FAIL or INCIDENT. +- ALWAYS promote confirmed learnings to the knowledge base. +- Be concise. One line per finding. No filler. + diff --git a/clowdex-download/.claude/.claude/command-index.md b/clowdex-download/.claude/.claude/command-index.md new file mode 100644 index 0000000..a6ceb86 --- /dev/null +++ b/clowdex-download/.claude/.claude/command-index.md @@ -0,0 +1,77 @@ +# Command Index + +All system commands, their triggers, required tools, and invocation mode. + +## Daily Rituals + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/start` | Beginning of work day | Read, Write, Edit, Bash(date) | Self-execute | Load memory, create daily note, review tasks | +| `/sync` | Mid-day (after 3-4 hours) | Read, Write, Edit, Bash(date), Agent | Self-execute | Refresh memory, process scratchpad, review tasks | +| `/end-day` | End of work day | Read, Write, Edit, Bash(date), Agent | Self-execute | Daily audit, externalize knowledge, prep tomorrow | +| `/standup` | Start of day (quick mode) | Read, Edit, Glob, Bash(git,date) | Self-execute | Auto-generate yesterday/today/blockers from git + tasks | +| `/flush` | Context pressure or task completion | Read, Write, Edit, Bash(date) | Self-execute | Distill state, flush context, auto-resume | + +## Quality & Review + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/audit [scope]` | After completing a task/feature | Read, Agent, Write, Edit | Self-execute | Delegate quality review to sentinel agent | +| `/review [target]` | Before merging code | Read, Agent, Glob, Grep, Bash(git) | Self-execute | Deep code review — security + performance + architecture | +| `/system-audit` | Monthly or after major changes | Read, Glob, Grep, Agent, Write, Edit, Bash(date,wc,find) | Self-execute | Deep infrastructure audit of entire system | +| `/check-drift` | Monthly or when behaviour feels off | Read, Agent, Glob, Grep, Bash(wc,find,date) | Self-execute | Detect config drift — stale rules, contradictions, orphans | +| `/retro [period]` | End of sprint/week | Read, Write, Edit, Glob, Agent, Bash(date) | Self-execute | Sprint retrospective — analyze patterns, improve process | +| `/tech-debt [dir]` | Before planning sprint work | Read, Agent, Glob, Grep, Bash(git,wc,find) | Self-execute | Map and prioritise technical debt across codebase | + +## Problem Solving + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/unstick [problem]` | When stuck on a problem 10+ min | Read, Agent, Grep, Glob, WebSearch | Self-execute | Root-cause analysis via pathfinder agent | +| `/onboard [project]` | Starting work on unfamiliar codebase | Read, Agent, Glob, Grep, Bash(git,find,wc,ls) | Self-execute | Generate full codebase onboarding guide | + +## Planning & Strategy + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/brief [idea]` | Starting a new project | Read, Write, Edit, Agent, Glob, Bash(date) | Self-execute | Turn rough idea into structured project brief | +| `/launch [product]` | Preparing to launch a product/feature | Read, Write, Edit, Agent, Glob, Grep, WebSearch, WebFetch, Bash(date) | Self-execute | Full launch pipeline — competitive scan to GTM checklist | +| `/proposal [project]` | Client asks for a proposal | Read, Write, Edit, Agent, Glob, Bash(date) | Self-execute | Generate structured client proposal with scope and pricing | +| `/market-scan [market]` | Entering a new market or evaluating position | Read, Write, Edit, Agent, Glob, WebSearch, WebFetch, Bash(date) | Self-execute | Deep competitive analysis with strategic recommendations | + +## Communication & Delivery + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/report [topic]` | Need to present findings to stakeholders | Read, Write, Edit, Agent, Glob, Grep, Bash(date) | Self-execute | Generate audience-aware professional report | +| `/release [version]` | Shipping a new version | Read, Write, Edit, Glob, Grep, Bash(git,date) | Self-execute | Auto-generate release notes — technical + marketing + executive | +| `/handoff [recipient]` | Passing work to another person or AI | Read, Write, Edit, Glob, Grep, Bash(git,date) | Self-execute | Structured session handoff with full context briefing | + +## System Building + +| Command | Trigger | Tools | Mode | Description | +|---------|---------|-------|------|-------------| +| `/create-playbook [name]` | Repeating a manual workflow | Read, Write, Edit, Glob, Bash(date) | Self-execute | Record a workflow and auto-generate a reusable command | + +## Auto-Trigger Conditions + +Commands should be proactively invoked (not waiting for user) when: + +| Condition | Command | +|-----------|---------| +| Session starts fresh | `/start` (if morning) or `/standup` (if quick) | +| 30+ tool calls in session | `/flush` | +| Compaction warning | `/flush` (emergency mode) | +| Discrete multi-step task completes | Consider `/flush` | +| Quality feels degraded | `/flush` | +| Stuck for 10+ minutes | `/unstick` | +| Feature/task completed | `/audit` | +| Before merging code | `/review` | +| Starting unfamiliar project | `/onboard` | +| Passing work to someone else | `/handoff` | +| System behaviour feels off | `/check-drift` | + +## Invocation Modes + +- **Self-execute**: Read the command file and follow the procedure directly +- **Recommend**: Output `RECOMMEND: /command [args] — [reason]` for the orchestrator diff --git a/clowdex-download/.claude/.claude/commands/audit.md b/clowdex-download/.claude/.claude/commands/audit.md new file mode 100644 index 0000000..7b28c2e --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/audit.md @@ -0,0 +1,68 @@ +--- +description: Run the sentinel agent against recent work or a specific file/task +argument-hint: "[scope]" +allowed-tools: + - Read + - Agent + - Write + - Edit +--- + +Delegate a quality review to the sentinel agent. + +## Steps + +### Step 1: Determine scope + +If the user provided a specific scope (file, task, or area): +- Use that as the audit target + +If no scope provided: +- Default to "today's work" — read the daily note for context + +### Step 2: Select audit tier + +| Tier | When | Depth | +|------|------|-------| +| T1 | Daily wrap-up, quick check | Scan for obvious issues, 2-3 min | +| T2 | After completing a feature or multi-step task | Check completeness, consistency, side effects | +| T3 | Weekly review, after major changes | Full regression check, knowledge-base sweep | +| T4 | Monthly or after system changes | Deep infrastructure audit, cross-file coherence | + +Default to T2 for explicit `/audit` calls. + +### Step 3: Delegate to sentinel + +Spawn the sentinel agent with the appropriate tier and scope: + +``` +Agent(sentinel): [Tier] audit of [scope]. + +Context: +- [Brief description of what was done] +- [Key files involved] + +Check for: +1. Completeness — were all requirements met? +2. Consistency — do changes align with existing patterns? +3. Side effects — did changes break anything downstream? +4. Knowledge — are there learnings to promote or nominate? + +Report findings as PASS/WARN/FAIL with specific file:line references. +``` + +### Step 4: Process results + +- **PASS**: Log success, note any suggestions +- **WARN**: Log warnings, add to daily note +- **FAIL**: Log failures, add to incident log, create corrective tasks on Task Board + +### Step 5: Update logs + +Append audit results to daily note under a new section: +```markdown +## Audit — HH:MM (T[tier]) +- Result: [PASS/WARN/FAIL] +- Findings: [bullets] +- Actions: [any corrective tasks created] +``` diff --git a/clowdex-download/.claude/.claude/commands/brief.md b/clowdex-download/.claude/.claude/commands/brief.md new file mode 100644 index 0000000..d8039b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/brief.md @@ -0,0 +1,148 @@ +--- +description: Turn a rough idea into a structured project brief +argument-hint: "[project idea]" +allowed-tools: + - Read + - Write + - Edit + - Agent + - Glob + - Bash(date:*) +--- + +Turn a rough idea into a structured project brief with requirements, user stories, acceptance criteria, risks, and timeline. + +## Steps + +### Step 1: Capture the idea + +Take whatever the user described and identify: +- **The problem:** What pain does this solve? +- **The solution:** What are we building? +- **The user:** Who benefits? +- **The outcome:** What does success look like? + +If any of these are unclear from the input, make reasonable assumptions and flag them. + +### Step 2: Define scope + +**In scope:** +- List specific capabilities / features this project will deliver +- Be concrete — "user can filter by date" not "filtering functionality" + +**Out of scope:** +- Explicitly list what this project will NOT do +- This is as important as in-scope — prevents scope creep + +**Assumptions:** +- What are we assuming to be true? +- Technical assumptions (platform, stack, integrations) +- Business assumptions (budget, timeline, team) + +### Step 3: User stories + +Write 5-10 user stories in standard format: + +``` +As a [user type], I want to [action] so that [benefit]. + +Acceptance criteria: +- [ ] [Specific, testable criterion] +- [ ] [Specific, testable criterion] +- [ ] [Specific, testable criterion] +``` + +Prioritise using MoSCoW: +- **Must have:** Non-negotiable for launch +- **Should have:** Important but not critical +- **Could have:** Nice to have if time allows +- **Won't have:** Explicitly excluded from this version + +### Step 4: Technical considerations + +If relevant: +- **Stack / platform:** Recommended technology choices +- **Integrations:** Third-party services or APIs needed +- **Data:** What data is needed, where it comes from, how it's stored +- **Constraints:** Performance requirements, security needs, compliance + +### Step 5: Risks and mitigations + +Identify the top 3-5 risks: + +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [risk] | High/Med/Low | High/Med/Low | [what to do about it] | + +### Step 6: Timeline estimate + +Break into phases with rough estimates: +- **Phase 1 — Foundation:** [scope] — [estimate] +- **Phase 2 — Core features:** [scope] — [estimate] +- **Phase 3 — Polish & launch:** [scope] — [estimate] + +Note: These are rough estimates, not commitments. + +### Step 7: Write the brief + +Save to `briefs/[project-name]-brief.md`: + +```markdown +# Project Brief — [Name] + +**Date:** [date] +**Status:** Draft + +--- + +## Problem +[What pain are we solving?] + +## Solution +[What are we building?] + +## Target User +[Who benefits?] + +## Success Criteria +[How do we know this worked?] + +## Scope + +### In Scope +- [specific feature] + +### Out of Scope +- [explicitly excluded] + +### Assumptions +- [assumption] + +## User Stories + +### Must Have +[user stories with acceptance criteria] + +### Should Have +[user stories] + +### Could Have +[user stories] + +## Technical Considerations +[stack, integrations, data, constraints] + +## Risks +[risk table] + +## Timeline +[phased estimate] + +## Open Questions +- [anything still unresolved] + +--- +Ready for review. +``` + +Output a summary and flag any open questions that need answers before work starts. diff --git a/clowdex-download/.claude/.claude/commands/check-drift.md b/clowdex-download/.claude/.claude/commands/check-drift.md new file mode 100644 index 0000000..68ed439 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/check-drift.md @@ -0,0 +1,98 @@ +--- +description: Detect system configuration drift - find stale rules, contradictions, and orphans +argument-hint: "" +allowed-tools: + - Read + - Agent + - Glob + - Grep + - Bash(wc:*, find:*, date:*) +--- + +Self-monitoring command. Scans your entire Claude Code configuration for drift — stale rules, contradictions, orphaned files, and configuration inconsistencies. + +## Steps + +### Step 1: Scan system files (parallel) + +Read all configuration sources simultaneously: +- `CLAUDE.md` — project instructions +- `.claude/memory.md` — active memory +- `.claude/knowledge-base.md` — learned rules +- `.claude/settings.json` — hooks configuration +- `.claude/command-index.md` — command registry (if exists) + +### Step 2: Check for contradictions + +**Within CLAUDE.md:** +- Are there conflicting instructions? (e.g., "always do X" and "never do X") +- Are there references to files or directories that don't exist? +- Are there references to commands or agents that aren't defined? + +**Between CLAUDE.md and knowledge-base:** +- Does the knowledge base contain rules that contradict CLAUDE.md? +- Are there duplicate rules across both files? + +**Between memory and reality:** +- Does memory reference tasks, files, or states that no longer exist? +- Are there "current focus" items that are clearly stale? + +### Step 3: Check for orphans + +Scan for: +- **Orphaned commands:** Files in `.claude/commands/` not referenced in command-index.md +- **Orphaned agents:** Agent definitions with no command or skill that invokes them +- **Orphaned skills:** Skills not referenced by any command, agent, or CLAUDE.md +- **Dead references:** Mentions of files, URLs, or paths that don't exist +- **Unused hooks:** Hook scripts that exist but aren't wired in settings.json + +### Step 4: Check for staleness + +- **Memory.md:** Is "Now" section from more than 3 days ago? +- **Knowledge-base entries:** Do any reference outdated tools, APIs, or patterns? +- **Daily notes:** Are there daily notes from 30+ days ago that should be archived? +- **Task Board:** Are there tasks that have been "in progress" for more than a week? + +### Step 5: Check configuration health + +- **settings.json:** Is it valid JSON? Are all hook scripts executable? +- **CLAUDE.md size:** Is it growing too large? (>500 lines is a warning) +- **Memory.md size:** Is it within limits? (<100 lines target) +- **Knowledge-base size:** Is it within limits? (<200 lines target) + +### Step 6: Generate drift report + +```markdown +# Drift Detection Report + +**Date:** [date] +**Status:** [CLEAN / WARNINGS / ISSUES FOUND] + +## Contradictions Found +- [contradiction with file references] + +## Orphaned Items +- [orphaned file or reference] + +## Stale Items +- [stale memory, task, or reference] + +## Configuration Health +| Check | Status | Note | +|-------|--------|------| +| settings.json valid | Pass/Fail | | +| CLAUDE.md size | [lines] | [ok / warning] | +| memory.md size | [lines] | [ok / warning] | +| knowledge-base size | [lines] | [ok / warning] | +| Hook scripts executable | Pass/Fail | | + +## Recommended Actions +1. [Specific fix] +2. [Specific fix] +3. [Specific fix] + +--- +Run monthly or when system behaviour feels off. +``` + +Output the status line and any critical issues. Offer to fix automatically if issues are simple. diff --git a/clowdex-download/.claude/.claude/commands/create-playbook.md b/clowdex-download/.claude/.claude/commands/create-playbook.md new file mode 100644 index 0000000..6a12eb8 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/create-playbook.md @@ -0,0 +1,87 @@ +--- +description: Record a workflow and auto-generate a reusable command from it +argument-hint: "[name for the playbook]" +allowed-tools: + - Read + - Write + - Edit + - Glob + - Bash(date:*) +--- + +Watch a manual workflow, then auto-generate a reusable command from it. You describe the steps, this command turns them into a repeatable, documented procedure. + +## Steps + +### Step 1: Name the playbook + +Get the playbook name from the argument. If not provided, ask what this workflow does in one sentence and derive a kebab-case name. + +### Step 2: Capture the workflow + +Ask the user to describe their workflow step by step. For each step, capture: +- **What:** The action taken +- **Where:** What file, tool, or system is involved +- **Why:** The purpose of this step +- **Inputs:** What information is needed +- **Output:** What this step produces + +Guide them through it: "What do you do first?" → "Then what?" → "What happens next?" + +Continue until they say they're done. + +### Step 3: Identify patterns + +Analyse the captured workflow: +- **Which steps can be parallelised?** (independent reads, searches) +- **Which steps need user input?** (decisions, approvals) +- **Which steps are conditional?** (only if X, then Y) +- **What tools does each step need?** (Read, Write, Agent, Bash, WebSearch, etc.) +- **Are there any existing skills that match steps?** (check `.claude/skills/`) + +### Step 4: Determine the argument + +What variable input does this workflow need each time it runs? +- A project name? A file path? A topic? A client name? +- Define the argument-hint that makes sense + +### Step 5: Generate the command + +Write the command file to `.claude/commands/[playbook-name].md`: + +```markdown +--- +description: [one-line description derived from the workflow] +argument-hint: "[identified argument]" +allowed-tools: + - [list of tools needed, derived from step analysis] +--- + +[Brief explanation of what this command does] + +## Steps + +### Step 1: [First action] +[Instructions derived from the captured workflow] + +### Step 2: [Second action] +[Instructions] + +[Continue for each step, with parallel steps marked] + +### Step [N]: Output +[What the final output looks like] +``` + +### Step 6: Verify and refine + +Show the generated command to the user: +- "Here's the command I generated. Does this capture your workflow correctly?" +- Make any adjustments they request +- Save the final version + +### Step 7: Register the command + +If a command-index.md exists, add the new command to it. + +Output: "Your playbook is saved as `/[name]`. Run it any time to repeat this workflow." diff --git a/clowdex-download/.claude/.claude/commands/end-day.md b/clowdex-download/.claude/.claude/commands/end-day.md new file mode 100644 index 0000000..7802a41 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/end-day.md @@ -0,0 +1,84 @@ +--- +description: End of day - sync memory, clear done list, externalize knowledge, prep tomorrow +argument-hint: "" +allowed-tools: + - Read + - Edit + - Write + - Bash(date:*) + - Agent +--- + +End-of-day ritual. Externalize knowledge, clean up, prepare for tomorrow. + +## Steps + +### Step 1: Read current state (parallel) + +Read simultaneously: +- `.claude/memory.md` +- `Daily Notes/MMDDYY.md` (today) +- `Scratchpad.md` +- `Task Board.md` + +### Step 2: Process remaining scratchpad items + +Same as /sync Step 2. Clear everything — scratchpad should be empty at end of day. + +### Step 3: Sync memory + +Edit `.claude/memory.md`: +- Update "Now" to reflect where things stand +- Resolve completed Open Threads +- Prune stale Recent Decisions (older than 1 week) +- Clear resolved Blockers + +### Step 4: Move completed tasks + +In `Task Board.md`: +- Move all completed tasks from Today → Done +- Clear Done list if it's Friday +- Move incomplete Today items to This Week or Backlog with a note on why + +### Step 5: Knowledge externalization + +Review today's work for learnings: +- **User corrections**: Anything the user explicitly corrected → nominate to `.claude/knowledge-nominations.md` +- **Empirical discoveries**: Things proven through testing → nominate +- **Pattern observations**: Recurring patterns noticed → nominate +- **Failure lessons**: Root cause of any resolved failures → nominate + +Format: `- [MMDDYY] /end-day: [learning] | Evidence: [source]` + +### Step 6: Mandatory daily audit + +Spawn the sentinel agent to review today's work: + +``` +Agent(sentinel): Review today's work in Daily Notes/MMDDYY.md. Check: +1. Were all tasks completed or properly deferred? +2. Were any knowledge-base rules violated? +3. Are there any pending nominations to review? +Tier: T1 (quick scan). Report findings. +``` + +### Step 7: Review incident log + +Read `.claude/logs/incident-log.md`. Summarize any notable events. + +### Step 8: Preview tomorrow + +Based on Task Board and Open Threads, suggest 1-3 priorities for tomorrow. +Add them to Task Board → Today. + +### Step 9: Update daily note + +Add to `Daily Notes/MMDDYY.md` → End of Day Summary: +- Key accomplishments +- Decisions made +- Open items carried forward +- Tomorrow's priorities + +### Step 10: Sign off + +Brief message: what was accomplished today, what's next tomorrow. diff --git a/clowdex-download/.claude/.claude/commands/flush.md b/clowdex-download/.claude/.claude/commands/flush.md new file mode 100644 index 0000000..1e03203 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/flush.md @@ -0,0 +1,90 @@ +--- +description: Safely flush context and resume fresh - distills session state before clearing +argument-hint: "" +allowed-tools: + - Read + - Edit + - Write + - Bash(date:*) +--- + +Persist session state then seamlessly resume work. The user should not notice this happening. + +**Emergency mode** (compacting/prompt-too-long): Skip reads, distill from in-context memory only, go to Step 3. + +--- + +## Steps + +### Step 0: Reset gate + get date + +```bash +date +"%m%d%y %H:%M" && rm -f ".claude/logs/.quality-gate-active" ".claude/logs/.session-blocks-$(date +"%m%d-%H")" ".claude/logs/.tool-call-count" ".claude/logs/.compaction-occurred" +``` + +### Step 1: Read state (parallel, skip in emergency) + +Read simultaneously: `.claude/memory.md` + `Daily Notes/MMDDYY.md` + +### Step 2: Distill session (from in-context memory) + +Extract and compress using **restorable compression** — preserve retrieval paths so the resumed session can restore full context from compressed form: + +1. **Task** — one sentence +2. **Done/remaining** — 2-4 bullets, conclusions not process +3. **Decisions** — one line each, WHAT+WHY not HOW +4. **Learnings** — rules/facts for knowledge-nominations +5. **Files touched** — full paths of every file read or modified (not just modified — include key files *read* that informed decisions). These are retrieval anchors for the resumed session. +6. **Active references** — URLs, API endpoints, external resources consulted. Drop content, keep the pointer. +7. **Next action** — precise, actionable instruction including which file(s) to read first + +### Step 3: Write handoff to daily note + +Append (or create new daily note if none exists): + +```markdown +## Session Handoff — HH:MM + +**Task:** [one sentence] +**Done:** [bullets] +**Remaining:** [bullets] +**Decisions:** [bullets] +**Files:** [full paths — both modified and key reads] +**Refs:** [URLs, external resources — pointers only, no content] +**Next:** [precise action + which file(s) to read first] +``` + +### Step 4: Update memory.md (only if changed) + +New priorities, threads, decisions → edit. Nothing changed → skip. + +### Step 5: Promote and nominate learnings (only if discovered) + +**Two-tier promotion:** + +**Tier 1: Immediate promotion to `knowledge-base.md`** (high-confidence rules): +- User overrides (explicitly corrected something) +- Empirical facts (verified through testing or data) + +Write directly with `[Source: User directive MMDDYY]` or `[Source: Empirical MMDDYY]`. + +**Tier 2: Nominate to `knowledge-nominations.md`** (lower-confidence): +- Agent inferences (patterns observed but not confirmed) +- Hypotheses (things that seem true but need more evidence) + +Append: `- [MMDDYY] /flush: [learning] | Evidence: [source]` + +**Rule: When in doubt, promote. A rule in knowledge-base.md that gets corrected later is better than a rule in nominations that never gets seen.** + +### Step 6: Auto-resume (restorable decompression) + +Do NOT output a resumption prompt. Do NOT ask the user anything. Instead: + +1. Re-read `.claude/memory.md` and `.claude/knowledge-base.md` (compressed context reload) +2. Re-read the daily note handoff you just wrote (for the Next action) +3. **Restore from retrieval anchors** — re-read the file(s) specified in the **Next** field and any critical files from the **Files** list that the next action depends on. This is the decompression step: the handoff told you *what* happened; re-reading the files restores *how* to continue. +4. **Immediately execute the Next action** — pick up exactly where you left off + +The user should experience a brief pause, then work continuing seamlessly. No visible "clearing" or "resuming" messages. Just keep working. + +Target: 5-7 tool calls, <30 seconds. Emergency: 2-3 calls, <15 seconds. diff --git a/clowdex-download/.claude/.claude/commands/handoff.md b/clowdex-download/.claude/.claude/commands/handoff.md new file mode 100644 index 0000000..19b11d5 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/handoff.md @@ -0,0 +1,105 @@ +--- +description: Structured session handoff to another person or AI +argument-hint: "[who you're handing off to]" +allowed-tools: + - Read + - Write + - Edit + - Glob + - Grep + - Bash(git log:*, git status:*, git diff:*, date:*) +--- + +Generate a structured handoff briefing when passing work to another person or AI. Captures context, decisions, risks, and next steps so nothing gets lost in transition. + +## Steps + +### Step 1: Gather session context + +Read: +- `.claude/memory.md` — current state +- Recent daily note — today's work log +- `Task Board.md` — active tasks and priorities +- `git status` and `git log --oneline -10` — recent changes + +### Step 2: Identify what was done + +From the session context and git history, list: +- **Completed:** Tasks finished in this session +- **In progress:** Work started but not finished (with current state) +- **Decisions made:** Choices and their rationale +- **Files touched:** Every file modified with a one-line summary of the change + +### Step 3: Identify what's pending + +- **Immediate next steps:** What should happen next (ordered) +- **Blocked items:** Tasks that can't proceed and why +- **Open questions:** Decisions that need input +- **Risks:** Anything that could go wrong if not handled + +### Step 4: Context the recipient needs + +- **Project context:** What is this project and what matters right now? +- **Key files:** Where to look for the most important things +- **Gotchas:** Non-obvious things that will trip someone up +- **Dependencies:** External people, services, or events this work depends on + +### Step 5: Write the handoff + +Save to `handoffs/handoff-[date]-[time].md`: + +```markdown +# Session Handoff + +**From:** [current session / your name] +**To:** [recipient if specified, otherwise "Next session"] +**Date:** [date and time] + +--- + +## Status Summary +[2-3 sentences: where things stand right now] + +## What Was Done +- [completed task with file references] +- [completed task] + +## What's In Progress +- **[task]** — Current state: [where it's at]. Next action: [what to do next] + +## Decisions Made +| Decision | Rationale | Reversible? | +|----------|-----------|-------------| +| [decision] | [why] | Yes/No | + +## Files Changed +| File | Change | +|------|--------| +| [path] | [one-line summary] | + +## Next Steps (Priority Order) +1. [Most important next action] +2. [Second priority] +3. [Third priority] + +## Blocked Items +- **[item]** — Blocked by: [reason]. Unblock by: [action needed] + +## Open Questions +- [Question that needs answering before proceeding] + +## Risks +- [Risk and what to do about it] + +## Key Files to Read +- [file] — [why it matters] +- [file] — [why it matters] + +## Gotchas +- [Non-obvious thing that will trip you up] + +--- +Handoff complete. Read this before starting work. +``` + +Output the summary section so the user can verify it's accurate. diff --git a/clowdex-download/.claude/.claude/commands/launch.md b/clowdex-download/.claude/.claude/commands/launch.md new file mode 100644 index 0000000..aad651a --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/launch.md @@ -0,0 +1,130 @@ +--- +description: Full product launch pipeline - from idea to go-to-market plan +argument-hint: "[product or feature to launch]" +allowed-tools: + - Read + - Write + - Edit + - Agent + - Glob + - Grep + - WebSearch + - WebFetch + - Bash(date:*) +--- + +Full launch pipeline. Takes a product or feature idea through competitive research, positioning, pricing analysis, and GTM planning. + +## Steps + +### Step 1: Capture the launch brief + +If the user described what they're launching, use that. Otherwise ask for: +- What is the product/feature? +- Who is the target customer? +- What's the timeline? + +Write a one-paragraph launch brief. + +### Step 2: Competitive scan (parallel agents) + +Spawn agents to research in parallel: + +**Agent 1 — Competitor landscape:** +- Search for direct competitors (products solving the same problem) +- Extract pricing, features, positioning, strengths, weaknesses +- Identify gaps in the market + +**Agent 2 — Market signals:** +- Search for recent trends in this space +- Look for demand signals (Reddit threads, HN discussions, Twitter conversations) +- Note any regulatory or platform changes that affect timing + +### Step 3: Positioning + +Based on competitive findings, define: +- **Category:** What market category does this belong to? +- **Differentiation:** What do you do that competitors don't? +- **Value prop:** One sentence that makes a customer say "I need this" +- **Positioning statement:** For [target], [product] is the [category] that [key benefit] unlike [alternative] because [reason] + +### Step 4: Pricing analysis + +Using competitor pricing data: +- Map competitor price points (free tier, entry, pro, enterprise) +- Identify the price range your market expects +- Recommend a pricing strategy with rationale +- Include pricing model (one-time, subscription, usage-based, freemium) + +### Step 5: Landing page brief + +Generate a structured landing page outline: +1. **Hero:** Headline, subheading, primary CTA +2. **Pain points:** 3-4 problems your target customer has +3. **Solution:** How your product solves them +4. **Features:** Top 5-6 features with benefits (not just descriptions) +5. **Social proof:** What type of proof would work (testimonials, stats, logos) +6. **Pricing:** Based on Step 4 analysis +7. **FAQ:** 5-6 questions your target customer would ask +8. **Final CTA:** Closing push + +### Step 6: Go-to-market checklist + +Generate a phased launch checklist: + +**Pre-launch (2-4 weeks before):** +- [ ] Landing page live +- [ ] Email capture / waitlist set up +- [ ] Launch announcement drafted +- [ ] Distribution channels identified (communities, newsletters, social) +- [ ] Early access / beta users lined up + +**Launch day:** +- [ ] Announce on primary channels +- [ ] Post on Product Hunt / HN / relevant communities +- [ ] Email waitlist +- [ ] Monitor for issues +- [ ] Respond to early feedback + +**Post-launch (1-2 weeks after):** +- [ ] Collect and address feedback +- [ ] Publish case studies / results +- [ ] Optimise based on conversion data +- [ ] Follow up with early users + +### Step 7: Write the launch plan + +Save everything to `launch-plan-[product-name].md`: + +```markdown +# Launch Plan — [Product Name] + +## Brief +[one paragraph] + +## Competitive Landscape +[table of competitors with pricing/features/positioning] + +## Positioning +[positioning statement and differentiation] + +## Pricing Strategy +[recommended pricing with rationale] + +## Landing Page Brief +[structured outline from Step 5] + +## Go-to-Market Checklist +[phased checklist from Step 6] + +## Timeline +[key dates and milestones] + +## Risks +[top 3 risks and mitigations] + +--- +Generated: [date] +``` + +Output a summary of the plan and ask the user what to execute first. diff --git a/clowdex-download/.claude/.claude/commands/market-scan.md b/clowdex-download/.claude/.claude/commands/market-scan.md new file mode 100644 index 0000000..b7ee075 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/market-scan.md @@ -0,0 +1,133 @@ +--- +description: Deep competitive analysis - research, compare, strategise +argument-hint: "[your product or market]" +allowed-tools: + - Read + - Write + - Edit + - Agent + - Glob + - WebSearch + - WebFetch + - Bash(date:*) +--- + +Deep competitive intelligence. Research competitors, extract positioning and pricing, generate strategic comparison and recommendations. + +## Steps + +### Step 1: Define the competitive frame + +Clarify: +- **Your product/service:** What are you competing with? +- **Market category:** What space are you in? +- **Known competitors:** Any the user already knows about? + +### Step 2: Research competitors (parallel agents) + +Spawn 2-3 agents to research in parallel: + +**Agent 1 — Direct competitors:** +- Search for products/services in the same category +- For each: name, URL, pricing, key features, target customer, funding/size +- Look at their landing pages, pricing pages, feature pages + +**Agent 2 — Adjacent competitors:** +- Search for alternative approaches to the same problem +- Products in adjacent categories that could expand into this space +- Open-source alternatives + +**Agent 3 — Market context:** +- Recent news, launches, shutdowns in this space +- Analyst reports or market sizing data +- Customer sentiment (reviews, Reddit, Twitter) + +### Step 3: Build the comparison matrix + +Create a structured comparison: + +| Dimension | Your Product | Competitor A | Competitor B | Competitor C | +|-----------|-------------|-------------|-------------|-------------| +| **Price** | | | | | +| **Target customer** | | | | | +| **Key differentiator** | | | | | +| **Strengths** | | | | | +| **Weaknesses** | | | | | +| **Feature 1** | | | | | +| **Feature 2** | | | | | + +### Step 4: Identify strategic insights + +Analyse the comparison for: + +**Gaps you can exploit:** +- Features competitors lack that customers want +- Price points nobody serves +- Customer segments being ignored +- Positioning angles nobody owns + +**Threats to watch:** +- Well-funded competitors making moves +- Feature convergence (everyone building the same thing) +- Platform risk (dependency on a platform that could compete) + +**Your unfair advantages:** +- What do you have that's hard to replicate? +- Speed, expertise, network, data, positioning? + +### Step 5: Strategic recommendations + +Based on the analysis: +1. **Positioning recommendation:** How to position against the field +2. **Pricing recommendation:** Where to price and why +3. **Feature priority:** What to build (and not build) based on competitive gaps +4. **Messaging:** Key claims that differentiate you +5. **Watch list:** Competitors to monitor closely and triggers for action + +### Step 6: Write the intel report + +Save to `market-scan-[market].md`: + +```markdown +# Competitive Intelligence — [Market/Product] + +**Date:** [date] + +## Market Overview +[2-3 sentences on the competitive landscape] + +## Competitor Profiles + +### [Competitor 1] +- **URL:** [url] +- **Pricing:** [pricing model and range] +- **Target:** [who they serve] +- **Strengths:** [bullets] +- **Weaknesses:** [bullets] + +[Repeat for each competitor] + +## Comparison Matrix +[Table from Step 3] + +## Strategic Insights + +### Gaps to Exploit +[bullets] + +### Threats to Watch +[bullets] + +### Your Advantages +[bullets] + +## Recommendations +1. [Specific, actionable recommendation] +2. [Specific, actionable recommendation] +3. [Specific, actionable recommendation] + +--- +Sources: [list all URLs and sources used] +``` + +Output a summary of key findings and top recommendation. diff --git a/clowdex-download/.claude/.claude/commands/onboard.md b/clowdex-download/.claude/.claude/commands/onboard.md new file mode 100644 index 0000000..c736e4f --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/onboard.md @@ -0,0 +1,125 @@ +--- +description: Onboard to a new codebase - architecture scan, key decisions, first tasks +argument-hint: "[project directory or repo URL]" +allowed-tools: + - Read + - Agent + - Glob + - Grep + - Bash(git log:*, find:*, wc:*, ls:*) +--- + +New project onboarding. Scans a codebase and generates a comprehensive orientation: architecture, key decisions, dependency map, environment setup, and first tasks. + +## Steps + +### Step 1: Locate the project + +If the user specified a directory, use that. Otherwise, use the current working directory. + +Verify it's a real project (has package.json, Cargo.toml, pyproject.toml, go.mod, or equivalent). + +### Step 2: Structural scan (parallel) + +**Scan 1 — Project identity:** +- Read README, CONTRIBUTING, CHANGELOG if they exist +- Read package.json / Cargo.toml / pyproject.toml for metadata +- Identify: language, framework, build tool, test framework +- Count: total files, lines of code, number of dependencies + +**Scan 2 — Architecture:** +- Map the directory structure (top 3 levels) +- Identify architectural pattern (MVC, hexagonal, monolith, microservices, serverless) +- Find entry points (main files, route definitions, handlers) +- Locate config files (env, yaml, json configs) + +**Scan 3 — Key files:** +- Find the 10 most-changed files (`git log --format='' --name-only | sort | uniq -c | sort -rn | head -20`) +- Find the largest files (likely important or problematic) +- Locate test directories and test patterns + +### Step 3: Dependency analysis + +- List direct dependencies with versions +- Flag any outdated or deprecated packages (check for major version gaps) +- Identify critical dependencies (the ones the project can't function without) +- Note any unusual or niche dependencies worth understanding + +### Step 4: Code patterns + +Read 3-5 representative files to identify: +- Naming conventions (camelCase, snake_case, etc.) +- Error handling patterns +- Logging approach +- State management (if frontend) +- Database access patterns (if backend) +- Authentication / authorisation approach + +### Step 5: Git archaeology + +```bash +git log --oneline -20 +``` + +From recent history: +- What's being actively worked on? +- Who are the main contributors? +- What's the commit style? (conventional commits, free-form, etc.) +- Any long-running branches? + +### Step 6: Generate the onboarding guide + +Save to `ONBOARDING.md` (or output directly): + +```markdown +# Onboarding Guide — [Project Name] + +## Quick Facts +- **Language:** [lang] / **Framework:** [framework] +- **Architecture:** [pattern] +- **Lines of code:** [count] +- **Dependencies:** [count direct] +- **Test framework:** [framework] +- **Build tool:** [tool] + +## Project Structure +``` +[directory tree, top 3 levels, annotated] +``` + +## Key Files to Read First +1. **[file]** — [why it matters] +2. **[file]** — [why it matters] +3. **[file]** — [why it matters] +4. **[file]** — [why it matters] +5. **[file]** — [why it matters] + +## Architecture Overview +[2-3 paragraphs explaining how the system works] + +## Code Patterns +- **Naming:** [convention] +- **Error handling:** [pattern] +- **State:** [approach] +- **Auth:** [approach] + +## Environment Setup +1. [Step to get running locally] +2. [Step] +3. [Step] + +## First Tasks to Tackle +These are good starter tasks to build familiarity: +1. [Specific, small task with file reference] +2. [Specific, small task with file reference] +3. [Specific, small task with file reference] + +## Watch Out For +- [Gotcha or non-obvious pattern] +- [Gotcha or non-obvious pattern] + +--- +Generated: [date] +``` + +Output a brief summary and highlight the most important thing to understand about this codebase. diff --git a/clowdex-download/.claude/.claude/commands/proposal.md b/clowdex-download/.claude/.claude/commands/proposal.md new file mode 100644 index 0000000..df2e2c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/proposal.md @@ -0,0 +1,131 @@ +--- +description: Generate a client proposal from a project brief +argument-hint: "[project or client name]" +allowed-tools: + - Read + - Write + - Edit + - Agent + - Glob + - Bash(date:*) +--- + +Turn a rough brief into a structured client proposal with scope, timeline, deliverables, and pricing. + +## Steps + +### Step 1: Gather the brief + +If the user provided project details, use those. Otherwise, ask for: +- Client / project name +- What do they need? (the problem) +- What's the desired outcome? +- Any constraints (budget range, timeline, technical requirements)? + +### Step 2: Scope definition + +Break the project into phases and deliverables: + +For each phase: +- **Phase name** and duration +- **Deliverables** — specific, tangible outputs +- **Dependencies** — what's needed to start this phase +- **Assumptions** — what you're assuming to be true + +Flag anything that could cause scope creep. Be explicit about what's included and what isn't. + +### Step 3: Timeline + +Create a realistic timeline: +- Map phases to calendar weeks +- Identify milestones (decision points, reviews, handoffs) +- Build in buffer for feedback rounds +- Note any hard deadlines or dependencies on the client + +### Step 4: Pricing + +Structure the pricing: +- **Option A (Recommended):** Full scope as described +- **Option B:** Reduced scope (MVP / Phase 1 only) +- **Optional add-ons:** Additional services that complement the core work + +For each option, list: total price, payment schedule, what's included, what's not. + +### Step 5: Terms + +Standard terms to include: +- Payment schedule and terms +- Revision policy (how many rounds of revisions) +- Ownership / IP transfer +- Timeline for acceptance / sign-off +- Cancellation terms + +### Step 6: Write the proposal + +Save to `proposals/[client-name]-proposal.md`: + +```markdown +# Proposal — [Project Name] + +**Prepared for:** [Client] +**Prepared by:** [Your name/company] +**Date:** [date] + +--- + +## Executive Summary + +[2-3 sentences: the problem, your solution, expected outcome] + +## Understanding + +[Restate the client's problem in your words — proves you listened] + +## Approach + +### Phase 1: [Name] — [duration] +**Deliverables:** +- [specific output] +- [specific output] + +### Phase 2: [Name] — [duration] +**Deliverables:** +- [specific output] +- [specific output] + +[Continue for each phase] + +## Timeline + +| Phase | Duration | Milestone | +|-------|----------|-----------| +| [Phase 1] | [weeks] | [key deliverable] | + +## Investment + +### Option A: Full Scope (Recommended) +[price, payment schedule, what's included] + +### Option B: Phase 1 Only +[price, payment schedule, what's included] + +### Optional Add-ons +- [add-on]: [price] + +## Terms + +- [Payment terms] +- [Revision policy] +- [Ownership] + +## Next Steps + +1. Review this proposal +2. [Specific action to proceed] +3. Kick-off call to align on details + +--- +Valid for 30 days from date above. +``` + +Output a summary and tell the user where the file is saved. diff --git a/clowdex-download/.claude/.claude/commands/release.md b/clowdex-download/.claude/.claude/commands/release.md new file mode 100644 index 0000000..97a291b --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/release.md @@ -0,0 +1,107 @@ +--- +description: Generate audience-aware release notes from git history +argument-hint: "[version or date range]" +allowed-tools: + - Read + - Write + - Edit + - Glob + - Grep + - Bash(git log:*, git tag:*, git diff:*, date:*) +--- + +Auto-generate release notes from git history. Produces audience-appropriate versions — technical changelog, marketing announcement, or executive summary — from the same data. + +## Steps + +### Step 1: Determine the range + +Figure out what commits to include: +- If user specified a version → find the tag range (e.g., `git log v1.2.0..v1.3.0`) +- If user specified dates → use date range (`git log --after="2025-01-01" --before="2025-02-01"`) +- If nothing specified → changes since last tag (`git log $(git describe --tags --abbrev=0)..HEAD`) + +### Step 2: Gather commit data + +```bash +git log [range] --format="%h %s" --no-merges +``` + +Also check: +- PR descriptions if available (`git log --merges` for merge commit messages) +- Any CHANGELOG entries +- Modified files to understand scope (`git diff --stat [range]`) + +### Step 3: Categorise changes + +Sort every change into: + +| Category | Icon | Example | +|----------|------|---------| +| **New Features** | Added | New capability, new endpoint, new component | +| **Improvements** | Changed | Performance boost, UX improvement, refactor | +| **Bug Fixes** | Fixed | Resolved issue, corrected behaviour | +| **Breaking Changes** | Breaking | API change, removed feature, migration needed | +| **Dependencies** | Deps | Updated packages, new dependencies | +| **Internal** | Internal | Tests, CI, docs, refactoring | + +### Step 4: Write release notes (3 versions) + +**Version 1 — Technical Changelog** (for developers): +```markdown +# [Version] — [Date] + +## Breaking Changes +- [change with migration instructions] + +## New Features +- [feature]: [description] ([commit hash]) + +## Improvements +- [improvement] ([commit hash]) + +## Bug Fixes +- [fix] ([commit hash]) + +## Dependencies +- Updated [package] from [old] to [new] +``` + +**Version 2 — Marketing Announcement** (for customers/public): +```markdown +# What's New in [Version] + +[1-2 sentence hook — the most exciting change] + +### [Feature Name] +[Benefit-focused description — what it means for the user, not how it works] + +### [Improvement] +[User-facing improvement with before/after if applicable] + +### Bug Fixes +[Summary — "Fixed X issues including..." — no commit hashes] +``` + +**Version 3 — Executive Summary** (for stakeholders): +```markdown +# Release Summary — [Version] + +**Impact:** [one sentence — what this release accomplishes] + +**Key changes:** +- [Top 3 changes, business-impact framing] + +**Metrics:** +- [X] features added +- [X] bugs fixed +- [X] files changed + +**Risk:** [any breaking changes or migration needs — or "None"] +``` + +### Step 5: Save and output + +Save to `releases/[version]-release-notes.md` with all three versions. + +Output the marketing version by default (most commonly needed), and mention the other versions are in the file. diff --git a/clowdex-download/.claude/.claude/commands/report.md b/clowdex-download/.claude/.claude/commands/report.md new file mode 100644 index 0000000..a904194 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/report.md @@ -0,0 +1,112 @@ +--- +description: Generate a professional report from data or findings - audience-aware +argument-hint: "[topic and audience]" +allowed-tools: + - Read + - Write + - Edit + - Agent + - Glob + - Grep + - Bash(date:*) +--- + +Turn raw data, findings, or research into a polished narrative report. Adapts tone and depth for the target audience. + +## Steps + +### Step 1: Clarify inputs + +Identify: +- **Topic:** What is this report about? +- **Data sources:** What files, findings, or data should feed into it? +- **Audience:** Who is reading this? (executive, technical team, client, board, general) +- **Format preference:** Brief (1-2 pages), standard (3-5 pages), or comprehensive (5+ pages) + +If the user didn't specify an audience, default to "professional — clear, direct, no jargon." + +### Step 2: Gather source material + +Read all relevant files and data. Scan for: +- Key findings and metrics +- Patterns and trends +- Comparisons (before/after, vs. benchmark, vs. competitor) +- Anomalies or concerns +- Recommendations that emerge from the data + +### Step 3: Structure for the audience + +**Executive audience:** +- Lead with the bottom line (recommendation or key finding) +- Use bullet points over paragraphs +- Include only metrics that drive decisions +- Keep under 2 pages +- End with clear next steps + +**Technical audience:** +- Lead with methodology +- Include detailed data and analysis +- Show your work (how you reached conclusions) +- Include caveats and limitations +- Reference source files + +**Client audience:** +- Lead with what matters to them (results, ROI, impact) +- Use their language, not yours +- Contextualise numbers ("+15% vs industry average of +3%") +- Include visual formatting (tables, bold key numbers) +- End with what happens next + +### Step 4: Write the report + +```markdown +# [Report Title] + +**Date:** [date] +**Prepared for:** [audience] + +--- + +## Summary + +[2-3 sentences: key finding, core recommendation, bottom line] + +## Key Findings + +### [Finding 1] +[Data, context, significance] + +### [Finding 2] +[Data, context, significance] + +### [Finding 3] +[Data, context, significance] + +## Analysis + +[Deeper interpretation — what the findings mean, patterns, comparisons] + +## Recommendations + +1. **[Action]** — [rationale and expected impact] +2. **[Action]** — [rationale and expected impact] +3. **[Action]** — [rationale and expected impact] + +## Next Steps + +- [ ] [Specific action with owner/timeline] + +--- +Sources: [list data sources used] +``` + +### Step 5: Quality check + +Before delivering, verify: +- [ ] Every claim has supporting data +- [ ] No jargon the audience wouldn't understand +- [ ] Recommendations are actionable (not vague) +- [ ] Numbers are consistent throughout +- [ ] Report answers "so what?" — not just "what" + +Save to `reports/[topic]-report.md` and output a summary. diff --git a/clowdex-download/.claude/.claude/commands/retro.md b/clowdex-download/.claude/.claude/commands/retro.md new file mode 100644 index 0000000..4c2b34d --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/retro.md @@ -0,0 +1,85 @@ +--- +description: Sprint retrospective - review what worked, what didn't, improve process +argument-hint: "[time period]" +allowed-tools: + - Read + - Write + - Edit + - Glob + - Agent + - Bash(date:*) +--- + +Retrospective analysis. Review a time period, extract patterns, improve the system. + +## Steps + +### Step 1: Determine scope + +If user specified a time period, use that. Otherwise default to "this week." + +### Step 2: Gather data (parallel reads) + +Read simultaneously: +- Recent daily notes (last 5-7 days) +- `.claude/logs/verdicts.jsonl` (session quality trends) +- `.claude/logs/incident-log.md` (issues and blocks) +- `.claude/logs/failure-log.md` (tool failures) +- `.claude/knowledge-nominations.md` (pending learnings) +- `Task Board.md` (completion rate) + +### Step 3: Analyze patterns + +**What went well?** +- Tasks completed on time +- Smooth workflows (no blocks) +- Learnings successfully captured +- Quality verdicts trending positive + +**What didn't go well?** +- Repeated failures (same error type) +- Blocked commands that should have been allowed +- Tasks that took much longer than expected +- Context flushes (/flush) needed frequently +- Quality verdict blocks + +**What to change?** +- Are there process bottlenecks? +- Are hooks too strict or too lenient? +- Are agents missing capabilities? +- Are commands missing or underused? + +### Step 4: Extract improvements + +For each identified improvement: +1. Is it a **knowledge-base rule**? → Promote directly +2. Is it a **process change**? → Add to Scratchpad for user review +3. Is it a **tool/config change**? → Create task on Task Board +4. Is it a **pattern to watch**? → Nominate to knowledge-nominations + +### Step 5: Write retro report + +Add to daily note: + +```markdown +## Retrospective — [period] + +### Went Well +- [bullets] + +### Didn't Go Well +- [bullets] + +### Action Items +- [ ] [specific improvement with owner] + +### Metrics +- Tasks completed: [X] +- Quality verdict pass rate: [X]% +- Incidents: [X] (CRITICAL: [X], HIGH: [X]) +- Context flushes: [X] +``` + +### Step 6: Create action items + +Add any actionable improvements to `Task Board.md` → This Week. diff --git a/clowdex-download/.claude/.claude/commands/review.md b/clowdex-download/.claude/.claude/commands/review.md new file mode 100644 index 0000000..733edf1 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/review.md @@ -0,0 +1,100 @@ +--- +description: Deep code review - security, performance, architecture, and actionable fixes +argument-hint: "[file, directory, or PR]" +allowed-tools: + - Read + - Agent + - Glob + - Grep + - Bash(git diff:*, git log:*, git show:*) +--- + +Comprehensive code review. Goes beyond style — checks security, performance, architecture, and generates actionable improvement suggestions. + +## Steps + +### Step 1: Determine scope + +Identify what to review: +- If user specified a file or directory → review that +- If user specified a PR or branch → `git diff main...HEAD` (or appropriate base) +- If nothing specified → review staged changes (`git diff --cached`) or recent commits + +### Step 2: Read the code + +Read all files in scope. For large diffs, focus on: +- New files (highest risk — no prior review) +- Files with the most changes +- Test files (or lack thereof) + +### Step 3: Multi-dimensional review (parallel agents) + +Spawn parallel review agents: + +**Agent 1 — Security review:** +- Input validation (SQL injection, XSS, command injection) +- Authentication / authorisation gaps +- Secrets or credentials in code +- Unsafe dependencies +- OWASP Top 10 checklist + +**Agent 2 — Performance review:** +- N+1 queries or unnecessary database calls +- Missing indexes (if schema visible) +- Unbounded loops or recursion +- Large memory allocations +- Missing caching opportunities +- Unnecessary re-renders (React) or recomputations + +**Agent 3 — Architecture review:** +- Does this follow existing patterns in the codebase? +- Is responsibility clearly separated? +- Are there circular dependencies? +- Is the abstraction level appropriate? (over-engineered or under-abstracted) +- Will this be easy to test, debug, and maintain? + +### Step 4: Compile findings + +Categorise each finding: + +| Severity | Meaning | +|----------|---------| +| **CRITICAL** | Must fix before merge — security vulnerability, data loss risk, breaking bug | +| **HIGH** | Should fix — performance issue, architectural concern, maintainability problem | +| **MEDIUM** | Consider fixing — code smell, minor inefficiency, readability improvement | +| **LOW** | Nit — style preference, naming suggestion, comment improvement | + +### Step 5: Generate the review + +Output a structured review: + +```markdown +## Code Review — [scope] + +### Summary +[1-2 sentences: overall assessment and top concern] + +### Critical Issues +- **[File:line]** — [issue and why it matters] + **Fix:** [specific code suggestion] + +### High Priority +- **[File:line]** — [issue] + **Fix:** [suggestion] + +### Medium Priority +- [bullets] + +### What's Good +- [specific things done well — always include positives] + +### Verdict +[APPROVE / APPROVE WITH CHANGES / REQUEST CHANGES] +[One sentence rationale] +``` + +### Step 6: Offer to fix + +Ask the user: "Want me to fix the critical and high-priority issues now?" + +If yes, apply fixes directly. If no, the review stands as documentation. diff --git a/clowdex-download/.claude/.claude/commands/standup.md b/clowdex-download/.claude/.claude/commands/standup.md new file mode 100644 index 0000000..44905d9 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/standup.md @@ -0,0 +1,74 @@ +--- +description: Quick daily standup - yesterday, today, blockers from git and tasks +argument-hint: "" +allowed-tools: + - Read + - Edit + - Glob + - Bash(git log:*, date:*) +--- + +Automated daily standup. Pulls from git history and task board to generate yesterday/today/blockers in 30 seconds. + +## Steps + +### Step 1: Get the date context + +```bash +date +"%m%d%y %A" +``` + +Determine yesterday (skip weekends if today is Monday → use Friday). + +### Step 2: Gather data (parallel) + +**Git activity (yesterday):** +```bash +git log --after="yesterday 00:00" --before="today 00:00" --oneline --no-merges +``` + +If no commits yesterday, try the last 2 days. + +**Task Board:** +Read `Task Board.md`: +- Items marked done recently +- Items currently in progress +- Items marked blocked + +**Daily note (yesterday):** +Read yesterday's daily note if it exists — scan for decisions, notes, and end-of-day summary. + +**Memory:** +Read `.claude/memory.md` → Now section for current focus. + +### Step 3: Generate the standup + +Format: + +```markdown +## Standup — [Day, Date] + +### Yesterday +- [What was accomplished — from git commits and task board] +- [Each item as a bullet, combining related commits] + +### Today +- [Priority tasks from task board and memory] +- [Ordered by importance] + +### Blockers +- [Anything marked blocked or flagged as waiting] +- [Or "None" if clear] +``` + +### Step 4: Append to daily note + +Add the standup to today's daily note under a `## Standup` section. + +If no daily note exists for today, create one first (follow the format from `/start`). + +### Step 5: Output + +Print the standup concisely. Keep it under 10 lines — standups should be fast. + +If there are blockers, highlight them. If everything is clear, say so. diff --git a/clowdex-download/.claude/.claude/commands/start.md b/clowdex-download/.claude/.claude/commands/start.md new file mode 100644 index 0000000..7ed47ef --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/start.md @@ -0,0 +1,73 @@ +--- +description: Start the day - load memory, open task board, ready to work +argument-hint: "" +allowed-tools: + - Read + - Edit + - Write + - Bash(date:*) +--- + +Begin a working session. Load context, create today's daily note, review tasks. + +## Steps + +### Step 1: Get today's date + +```bash +date +"%m%d%y %H:%M %A" +``` + +### Step 2: Load memory (parallel reads) + +Read simultaneously: +- `.claude/memory.md` +- `.claude/knowledge-base.md` + +These are your working context. Knowledge-base entries are mandatory constraints. + +### Step 3: Create daily note + +Create `Daily Notes/MMDDYY.md` (if it doesn't exist): + +```markdown +# MMDDYY - Daily Work Log + +## Decisions +- + +## Meetings & Conversations +- + +## Notes +- + +## End of Day Summary +- +``` + +### Step 4: Open task board + +Read `Task Board.md`. Scan for: +- Overdue items (anything from previous days still open) +- Today's priorities +- Blocked items + +### Step 5: Task review + +For each task in Today: +1. Is it still relevant? +2. Do I have what I need to start? +3. Are there dependencies? + +Move stale tasks to Backlog. Flag blocked items. + +### Step 6: Ready to work + +Output a brief orientation: +- What day it is +- Top 1-3 priorities for today +- Any blockers or open threads from memory.md +- "Ready to work. What's first?" + +Keep it short. The user wants to start working, not read a report. diff --git a/clowdex-download/.claude/.claude/commands/sync.md b/clowdex-download/.claude/.claude/commands/sync.md new file mode 100644 index 0000000..d412836 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/sync.md @@ -0,0 +1,77 @@ +--- +description: Mid-day sync - review daily note, update memory, process notes +argument-hint: "" +allowed-tools: + - Read + - Edit + - Write + - Bash(date:*) +--- + +Mid-day context refresh. Process captured notes, update memory, health check. + +## Steps + +### Step 1: Read current state (parallel) + +Read simultaneously: +- `.claude/memory.md` +- `Daily Notes/MMDDYY.md` (today's date) +- `Scratchpad.md` + +### Step 2: Process scratchpad + +For each item in Scratchpad: +- Is it a task? → Move to Task Board +- Is it a decision? → Add to Daily Note → Decisions +- Is it a learning? → Nominate to `.claude/knowledge-nominations.md` +- Is it a note? → Add to Daily Note → Notes +- Is it stale? → Delete + +Clear processed items from Scratchpad. + +### Step 3: Scan task board + +Read `Task Board.md`: +- Move completed tasks from Today → Done +- Flag any tasks that are blocked +- Check if priorities have shifted + +### Step 4: Context health check + +Self-assess: +- Am I still oriented on the right problem? +- Have I been going in circles on anything? +- Is my context getting heavy? (If yes, consider `/flush` after sync) + +### Step 5: Orientation check (Boyd's Law) + +Ask yourself: +- What has changed since this morning? +- What assumptions am I making that might be wrong? +- What's the simplest next action? + +### Step 6: Update memory + +Edit `.claude/memory.md`: +- Update "Now" with current focus +- Add/resolve items in "Open Threads" +- Record any new decisions in "Recent Decisions" +- Update "Blockers" if anything changed + +### Step 7: Review incident log + +Read `.claude/logs/incident-log.md` (if it exists). Look for: +- Repeated failures (same error 3+ times) +- Blocked commands that should be allowed (or vice versa) +- Any CRITICAL severity events + +Report anything noteworthy to the user. + +### Step 8: Status report + +Brief summary: +- What was accomplished this morning +- Current focus +- Any blockers or changes in priority +- Suggested next action diff --git a/clowdex-download/.claude/.claude/commands/system-audit.md b/clowdex-download/.claude/.claude/commands/system-audit.md new file mode 100644 index 0000000..ddbdd2f --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/system-audit.md @@ -0,0 +1,92 @@ +--- +description: Deep infrastructure audit of the entire operating system +argument-hint: "" +allowed-tools: + - Read + - Glob + - Grep + - Agent + - Write + - Edit + - Bash(date:*,wc:*,find:*) +--- + +Comprehensive infrastructure audit. Run monthly or after major system changes. + +## Checks + +### Check 1: Agent Health +- Read every file in `.claude/agents/*.md` +- Verify each has valid frontmatter (---) +- Verify no TBD/TODO markers +- Check that referenced tools exist +- Check agent-memory directories exist for agents that need them + +### Check 2: Command Health +- Read every file in `.claude/commands/*.md` +- Verify each has valid frontmatter +- Check that allowed-tools are reasonable +- Verify no broken cross-references to other commands + +### Check 3: Hook Health +- Verify `.claude/settings.json` is valid JSON +- Check every hook script referenced in settings.json exists +- Verify all hook scripts are executable (chmod +x) +- Run a dry test: each hook should exit 0 with empty input + +### Check 4: Memory Tier Health +- `memory.md`: Is it under 100 lines? Is "Now" current? +- `knowledge-base.md`: Is it under 200 lines? Do all entries have [Source:]? +- `knowledge-nominations.md`: Are there stale nominations (>30 days)? +- `agent-memory/`: Do directories match existing agents? +- Daily Notes: Are recent notes present? + +### Check 5: Log Health +- `audit-trail.md`: Is it under 5000 lines? +- `incident-log.md`: Are there unresolved CRITICAL/HIGH events? +- `failure-log.md`: Are there recurring patterns? +- `verdicts.jsonl`: What's the block rate? Any task-type clustering? + +### Check 6: Permission & Config Coherence +- `.claude/settings.json` hooks match actual hook files +- No orphaned hook scripts (exist but not referenced) +- No missing hook scripts (referenced but don't exist) + +### Check 7: Cross-File Coherence +- CLAUDE.md references match actual file locations +- Command-index.md matches actual commands +- No circular dependencies between commands + +### Check 8: Backup & Storage +- `.claude/backups/`: Is auto-pruning working? (no dirs >7 days old) +- Large files in project root that shouldn't be there? + +### Check 9: Via Negativa Sweep +- Are there files/agents/commands that are never used? +- Could any hook be removed without loss? +- Is there duplicated logic between agents? +- Propose removals — simpler is better + +## Grading + +| Grade | Criteria | +|-------|----------| +| A | All checks pass, no issues | +| B | Minor issues only (cosmetic, non-blocking) | +| C | Some issues need attention (missing provenance, stale nominations) | +| D | Structural issues (broken hooks, invalid JSON, missing agents) | +| F | Critical failures (security issues, data loss risk) | + +## Output + +Write results to daily note under: +```markdown +## System Audit — MMDDYY + +**Grade:** [A-F] +**Checks:** [passed]/9 +**Issues:** [bullets with severity] +**Actions:** [corrective tasks, if any] +``` + +Create corrective tasks on Task Board for any D or F grade issues. diff --git a/clowdex-download/.claude/.claude/commands/tech-debt.md b/clowdex-download/.claude/.claude/commands/tech-debt.md new file mode 100644 index 0000000..a918ba2 --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/tech-debt.md @@ -0,0 +1,116 @@ +--- +description: Map and prioritise technical debt across your codebase +argument-hint: "[directory or project]" +allowed-tools: + - Read + - Agent + - Glob + - Grep + - Bash(git log:*, wc:*, find:*) +--- + +Scan a codebase for technical debt. Score files by complexity, test coverage, age, and known issues. Output a prioritised debt payoff plan. + +## Steps + +### Step 1: Define scope + +If the user specified a directory, use that. Otherwise scan the entire project (excluding node_modules, .git, vendor, build directories). + +### Step 2: Automated scans (parallel agents) + +**Agent 1 — TODO/FIXME/HACK scan:** +- Search for TODO, FIXME, HACK, XXX, TEMP, WORKAROUND comments +- For each: file, line, content, age (git blame) +- Categorise: technical debt, missing feature, known bug, cleanup needed + +**Agent 2 — Complexity hotspots:** +- Find the largest files (by line count) +- Find files with the deepest nesting (proxy for complexity) +- Find files with the most functions/methods +- Identify files changed most frequently (`git log --format='' --name-only | sort | uniq -c | sort -rn | head -20`) +- Cross-reference: files that are BOTH complex AND frequently changed are top priority + +**Agent 3 — Code health signals:** +- Check for deprecated API usage (grep for @deprecated, console.warn deprecation patterns) +- Find unused exports or dead code patterns +- Check dependency health (outdated packages in package.json / requirements.txt) +- Look for duplicated code patterns (similar function signatures, copy-paste indicators) + +### Step 3: Score each debt item + +Score on two dimensions: + +**Impact (how much it hurts):** +- 3 = Affects users, causes bugs, blocks features +- 2 = Slows development, makes changes risky +- 1 = Code smell, readability issue, style concern + +**Effort (how hard to fix):** +- 3 = Major refactor, multiple files, breaking changes +- 2 = Moderate work, contained to one area +- 1 = Quick fix, under an hour + +**Priority = Impact / Effort** — high impact + low effort = fix first. + +### Step 4: Generate the debt map + +```markdown +# Technical Debt Map — [Project] + +**Date:** [date] +**Files scanned:** [count] +**Debt items found:** [count] + +## Summary +- **Critical (fix now):** [count] +- **High (fix this sprint):** [count] +- **Medium (schedule it):** [count] +- **Low (when convenient):** [count] + +## Hotspots +Files with the most concentrated debt: + +| File | Debt Items | Complexity | Change Frequency | Priority | +|------|-----------|------------|-----------------|----------| +| [file] | [count] | [high/med/low] | [commits/month] | Critical | + +## Debt Inventory + +### Critical Priority +1. **[file:line]** — [description] + - Impact: [3] / Effort: [1] + - Recommendation: [specific action] + +### High Priority +[items] + +### Medium Priority +[items] + +### Low Priority +[items] + +## Payoff Plan + +### This Week +- [ ] [specific fix with file reference] +- [ ] [specific fix] + +### This Month +- [ ] [larger refactor] +- [ ] [dependency updates] + +### Backlog +- [ ] [items to schedule later] + +## Metrics to Track +- Total TODO/FIXME count (currently: [X]) +- Average file complexity score +- Outdated dependency count (currently: [X]) + +--- +Re-run this command monthly to track progress. +``` + +Output the summary and top 3 items to fix first. diff --git a/clowdex-download/.claude/.claude/commands/unstick.md b/clowdex-download/.claude/.claude/commands/unstick.md new file mode 100644 index 0000000..14ab50a --- /dev/null +++ b/clowdex-download/.claude/.claude/commands/unstick.md @@ -0,0 +1,64 @@ +--- +description: When you're stuck on a problem - get unstuck fast +argument-hint: "[what you're stuck on]" +allowed-tools: + - Read + - Agent + - Grep + - Glob + - WebSearch +--- + +Break through a block. Uses the Pathfinder agent for root-cause analysis and fresh approaches. + +## Steps + +### Step 1: Capture the stuck state + +If the user described what they're stuck on, use that. Otherwise, infer from: +- Current memory.md → Now +- Recent daily note entries +- Last few tool calls in context + +Articulate the block in one sentence: "I'm stuck on [X] because [Y]." + +### Step 2: Classify the block + +| Type | Signals | Approach | +|------|---------|----------| +| **Knowledge gap** | "I don't know how to..." | Search docs, read source, check knowledge-base | +| **Decision paralysis** | "I can't decide between..." | List tradeoffs, pick the reversible option | +| **Circular debugging** | Same error 3+ times | Step back, restate the problem, try opposite approach | +| **Scope confusion** | "This is bigger than I thought" | Scope check — are you solving the right problem? | +| **Environmental** | Build/deploy/config issues | Check logs, verify prerequisites, try clean state | + +### Step 3: Deploy the Pathfinder + +Spawn the pathfinder agent: + +``` +Agent(pathfinder): I'm stuck on [problem]. + +What I've tried: [list attempts] +Error/symptom: [what's happening] +Expected: [what should happen] + +Break this down. What am I missing? +``` + +### Step 4: Execute the suggestion + +Take the pathfinder's top recommendation and try it immediately. +Don't deliberate — act. The fastest way out of stuck is through. + +### Step 5: Log the resolution + +If resolved, add to daily note: +```markdown +### Unstick — HH:MM +- **Block:** [what was stuck] +- **Root cause:** [why] +- **Fix:** [what worked] +``` + +If the fix reveals a pattern, nominate to knowledge-nominations.md. diff --git a/clowdex-download/.claude/.claude/hooks/backup-before-write.sh b/clowdex-download/.claude/.claude/hooks/backup-before-write.sh new file mode 100755 index 0000000..3e6fdab --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/backup-before-write.sh @@ -0,0 +1,29 @@ +#!/bin/bash +# PreToolUse async hook — creates timestamped backups before Write|Edit. +# Runs asynchronously so it doesn't block the write operation. +# Keeps 7 days of backups, auto-prunes older ones. + +INPUT=$(cat) +FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty') + +# Skip if no file path or file doesn't exist yet +[ -z "$FILE_PATH" ] && exit 0 +[ ! -f "$FILE_PATH" ] && exit 0 + +# Skip if file is in logs or backups (no backup recursion) +case "$FILE_PATH" in + */.claude/logs/*|*/.claude/backups/*) exit 0 ;; +esac + +BACKUP_DIR="$CLAUDE_PROJECT_DIR/.claude/backups/$(date +%Y-%m-%d)" +mkdir -p "$BACKUP_DIR" + +# Create backup with timestamp suffix +BASENAME=$(basename "$FILE_PATH") +TIMESTAMP=$(date +"%H%M%S") +cp "$FILE_PATH" "$BACKUP_DIR/${BASENAME}.${TIMESTAMP}.bak" 2>/dev/null + +# Prune backups older than 7 days +find "$CLAUDE_PROJECT_DIR/.claude/backups" -maxdepth 1 -type d -mtime +7 -exec rm -rf {} \; 2>/dev/null + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/completeness-gate.sh b/clowdex-download/.claude/.claude/hooks/completeness-gate.sh new file mode 100755 index 0000000..cf7593a --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/completeness-gate.sh @@ -0,0 +1,190 @@ +#!/bin/bash +# PreToolUse completeness gate for Write|Edit tools. +# Uses structured JSON output: exit 0 + JSON stdout for both allow and deny. +# +# Validates content completeness for critical system files before allowing writes. +# Each file path gets path-specific validation rules. Non-critical files pass through. +# +# Philosophy: Only gate files where an incomplete write causes persistent damage. +# Daily notes, scratchpad, logs, templates = ungated (iterative by nature). +# Knowledge-base, settings, memory = gated (errors persist/cascade). + +INPUT=$(cat) +FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty') +TOOL=$(echo "$INPUT" | jq -r '.tool_name // empty') +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +INCIDENT_LOG="$LOG_DIR/incident-log.md" + +mkdir -p "$LOG_DIR" + +# Skip if no file path +[ -z "$FILE_PATH" ] && exit 0 + +# Get content based on tool type +if [ "$TOOL" = "Write" ]; then + CONTENT=$(echo "$INPUT" | jq -r '.tool_input.content // empty') +elif [ "$TOOL" = "Edit" ] || [ "$TOOL" = "MultiEdit" ]; then + CONTENT=$(echo "$INPUT" | jq -r '.tool_input.new_string // empty') +else + exit 0 +fi + +# Skip if no content to validate +[ -z "$CONTENT" ] && exit 0 + +# Get relative path for matching +RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}" + +log_incident() { + local SEVERITY="$1" + local MSG="$2" + echo "- \`$TIMESTAMP\` | COMPLETENESS | $SEVERITY | $MSG" >> "$INCIDENT_LOG" +} + +block() { + local FILE="$1" + local MSG="$2" + local SUGGESTION="${3:-Fix the content, then retry the write.}" + log_incident "MEDIUM" "BLOCKED: $MSG → $FILE" + jq -n \ + --arg reason "$MSG" \ + --arg file "$FILE" \ + --arg suggestion "$SUGGESTION" \ + '{ + hookSpecificOutput: { + hookEventName: "PreToolUse", + permissionDecision: "deny", + permissionDecisionReason: ("COMPLETENESS GATE: " + $reason + " | File: " + $file), + additionalContext: ("Write blocked by completeness gate. Issue: " + $reason + ". Suggestion: " + $suggestion) + } + }' + exit 0 +} + +block_high() { + local FILE="$1" + local MSG="$2" + local SUGGESTION="${3:-Fix the content, then retry the write.}" + log_incident "HIGH" "BLOCKED: $MSG → $FILE" + jq -n \ + --arg reason "$MSG" \ + --arg file "$FILE" \ + --arg suggestion "$SUGGESTION" \ + '{ + hookSpecificOutput: { + hookEventName: "PreToolUse", + permissionDecision: "deny", + permissionDecisionReason: ("COMPLETENESS GATE [HIGH]: " + $reason + " | File: " + $file), + additionalContext: ("Write blocked by completeness gate (HIGH severity). Issue: " + $reason + ". Suggestion: " + $suggestion) + } + }' + exit 0 +} + +# ═══════════════════════════════════════════════════════ +# SECRET EXPOSURE CHECK (runs on ALL files) +# Blocks writes containing API keys/tokens/secrets to +# non-.env files. Catches accidental credential leaks. +# ═══════════════════════════════════════════════════════ + +# Allow .env files and backups to contain secrets (that's where they belong) +IS_ENV_FILE=false +case "$RELATIVE_PATH" in + *.env*|.claude/backups/*) IS_ENV_FILE=true ;; +esac + +if [ "$IS_ENV_FILE" = "false" ]; then + # Check for common secret patterns in content being written + if echo "$CONTENT" | grep -qE '(sk[-_](live|test|ant|proj)[_-][A-Za-z0-9]{20,}|ghp_[A-Za-z0-9]{36}|ghs_[A-Za-z0-9]{36}|eyJhbGci[A-Za-z0-9+/=]{50,}|AKIA[0-9A-Z]{16}|xox[bpsar]-[A-Za-z0-9-]{20,})'; then + block_high "$RELATIVE_PATH" "SECURITY: Content contains what appears to be an API key, token, or secret. Credentials must NEVER be written to non-.env files." "Remove the credential from the content. Reference the secret by its variable name (e.g., STRIPE_SECRET_KEY) instead of its value. Secrets belong in .env files only." + fi +fi + +# ═══════════════════════════════════════════════════════ +# INCOMPLETE MARKER CHECK +# Shared logic for TBD/TODO/FIXME/PLACEHOLDER detection +# ═══════════════════════════════════════════════════════ +check_incomplete_markers() { + local content="$1" + local file="$2" + + # TBD, TODO, FIXME, PLACEHOLDER markers + if echo "$content" | grep -qiE '\bTBD\b|\bTODO\b|\bFIXME\b|\[PLACEHOLDER\]|\[INSERT '; then + block "$file" "Contains TBD/TODO/FIXME/PLACEHOLDER markers. Content must be investigation-complete." "Replace all placeholder markers with actual values. Search for TBD, TODO, FIXME, [PLACEHOLDER], and [INSERT in your content." + fi + + # Deferred decisions / open questions + if echo "$content" | grep -qiE 'assess whether|decide later|need to determine|open question|to be decided|deferred decision'; then + block "$file" "Contains deferred decisions or open questions. Resolve all decisions before writing." "Remove phrases like 'assess whether', 'decide later', 'need to determine', 'open question'. Make definitive statements instead." + fi +} + +# ═══════════════════════════════════════════════════════ +# PATH-SPECIFIC GATES +# ═══════════════════════════════════════════════════════ + +case "$RELATIVE_PATH" in + + # ─── KNOWLEDGE BASE ───────────────────────────────── + # Institutional memory. Errors here persist forever. + # Rules: provenance required, max 200 lines, no TBD. + ".claude/knowledge-base.md") + check_incomplete_markers "$CONTENT" "$RELATIVE_PATH" + + if [ "$TOOL" = "Write" ]; then + # Every bold entry line (- **...**) must have a [Source: ...] tag + ENTRY_COUNT=$(echo "$CONTENT" | grep -cE '^\s*-\s+\*\*' || true) + SOURCE_COUNT=$(echo "$CONTENT" | grep -cE '\[Source:' || true) + + if [ "$ENTRY_COUNT" -gt 0 ] && [ "$SOURCE_COUNT" -lt "$ENTRY_COUNT" ]; then + MISSING=$((ENTRY_COUNT - SOURCE_COUNT)) + block_high "$RELATIVE_PATH" "Knowledge-base has $MISSING entries missing [Source: ...] provenance. Every entry MUST cite its source." "Add [Source: user override MMDDYY] or [Source: empirical — description] or [Source: agent inference — description] to every entry line (- **...**:)." + fi + + # Max 200 lines + LINE_COUNT=$(echo "$CONTENT" | wc -l | tr -d ' ') + if [ "$LINE_COUNT" -gt 200 ]; then + block_high "$RELATIVE_PATH" "Knowledge-base is $LINE_COUNT lines (max 200). Curate: remove stale entries before adding new ones." "Read the current knowledge-base, identify entries older than 90 days or superseded by newer entries, remove them, then retry." + fi + fi + ;; + + # ─── MEMORY ───────────────────────────────────────── + # Active context. Must stay compact. + # Rules: max 100 lines (Write only). + ".claude/memory.md") + if [ "$TOOL" = "Write" ]; then + LINE_COUNT=$(echo "$CONTENT" | wc -l | tr -d ' ') + if [ "$LINE_COUNT" -gt 100 ]; then + block "$RELATIVE_PATH" "memory.md is $LINE_COUNT lines (max 100). Prune stale items before writing." "Remove completed items from Now, resolved items from Open Threads, and outdated entries from Recent Decisions." + fi + fi + ;; + + # ─── SETTINGS.JSON ───────────────────────────────── + # Hook configuration. Broken JSON = all hooks break. + # Rules: must be valid JSON. + ".claude/settings.json") + if [ "$TOOL" = "Write" ]; then + if ! echo "$CONTENT" | jq empty 2>/dev/null; then + block_high "$RELATIVE_PATH" "settings.json would be invalid JSON. Syntax error will break ALL hooks." "Validate JSON syntax: check for trailing commas, missing quotes, unmatched braces. Use Edit instead of Write to make targeted changes." + fi + fi + ;; + + # ─── AGENT DEFINITIONS ────────────────────────────── + # Agent instructions. Must be definitive, not speculative. + # Rules: no TBD/TODO. + .claude/agents/*.md) + check_incomplete_markers "$CONTENT" "$RELATIVE_PATH" + ;; + + # ─── ALL OTHER FILES: PASS THROUGH ───────────────── + *) + exit 0 + ;; + +esac + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/guard-bash.sh b/clowdex-download/.claude/.claude/hooks/guard-bash.sh new file mode 100755 index 0000000..dce1cf5 --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/guard-bash.sh @@ -0,0 +1,154 @@ +#!/bin/bash +# PreToolUse hook for Bash commands. +# Uses structured JSON output for blocks (exit 0 + JSON stdout). +# Falls through with plain exit 0 for allowed commands. +# +# Three tiers: +# HARD BLOCK — always blocked, no override (permissionDecision: deny) +# SOFT BLOCK — blocked with explanation, user can re-request (permissionDecision: deny) +# LOG WARNING — allowed but logged to incident log (exit 0, no JSON) + +INPUT=$(cat) +COMMAND=$(echo "$INPUT" | jq -r '.tool_input.command // empty') +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +INCIDENT_LOG="$LOG_DIR/incident-log.md" + +mkdir -p "$LOG_DIR" + +log_incident() { + local SEVERITY="$1" + local MSG="$2" + echo "- \`$TIMESTAMP\` | GUARD | $SEVERITY | $MSG" >> "$INCIDENT_LOG" +} + +deny() { + local REASON="$1" + local CONTEXT="$2" + jq -n \ + --arg reason "$REASON" \ + --arg context "$CONTEXT" \ + '{ + hookSpecificOutput: { + hookEventName: "PreToolUse", + permissionDecision: "deny", + permissionDecisionReason: $reason, + additionalContext: $context + } + }' + exit 0 +} + +# ═══════════════════════════════════════════════════════ +# HARD BLOCK — never allowed, no exceptions +# ═══════════════════════════════════════════════════════ + +# rm -rf / or rm -rf ~ (catastrophic) +if echo "$COMMAND" | grep -qE 'rm\s+(-[a-zA-Z]*f[a-zA-Z]*\s+)?(/|~|\$HOME)\s*$'; then + log_incident "CRITICAL" "BLOCKED: catastrophic rm → $COMMAND" + deny "HARD BLOCK: This would delete your entire filesystem or home directory." "Command blocked: catastrophic rm detected. This command is never allowed under any circumstances." +fi + +# git push --force (any branch) +if echo "$COMMAND" | grep -qE 'git\s+push\s+.*--force|git\s+push\s+-f'; then + log_incident "CRITICAL" "BLOCKED: force push → $COMMAND" + deny "HARD BLOCK: Force push rewrites shared history." "Command blocked: force push detected. Ask the user to confirm the specific branch if intentional." +fi + +# git reset --hard (destroys uncommitted work) +if echo "$COMMAND" | grep -qE 'git\s+reset\s+--hard'; then + log_incident "HIGH" "BLOCKED: git reset --hard → $COMMAND" + deny "HARD BLOCK: git reset --hard destroys uncommitted changes." "Command blocked: git reset --hard. Suggest using git stash or git commit first." +fi + +# git clean -f (deletes untracked files permanently) +if echo "$COMMAND" | grep -qE 'git\s+clean\s+(-[a-zA-Z]*f|-f)'; then + log_incident "HIGH" "BLOCKED: git clean -f → $COMMAND" + deny "HARD BLOCK: git clean -f permanently deletes untracked files." "Command blocked: git clean -f. Suggest using git stash instead." +fi + +# chmod 777 (security risk) +if echo "$COMMAND" | grep -qE 'chmod\s+777'; then + log_incident "HIGH" "BLOCKED: chmod 777 → $COMMAND" + deny "HARD BLOCK: chmod 777 grants full access to all users." "Command blocked: chmod 777. Use more restrictive permissions like 755 or 644." +fi + +# ═══════════════════════════════════════════════════════ +# SECRET EXPOSURE — block commands that leak credentials +# ═══════════════════════════════════════════════════════ + +# Block cat/head/tail/less of .env files (prevents full credential dump) +if echo "$COMMAND" | grep -qE '(cat|head|tail|less|more|bat)\s+.*(\.(env|env\.local|env\.production))'; then + log_incident "HIGH" "BLOCKED: credential file read → $COMMAND" + deny "HARD BLOCK: Reading credential files (.env) via shell exposes secrets in output." "Use environment variable names (e.g., \$DATABASE_URL) instead of reading the file. If you need to verify a value exists, use: grep -c 'KEY_NAME' file" +fi + +# Block echo/printf of environment variables containing common secret prefixes +if echo "$COMMAND" | grep -qE '(echo|printf)\s+.*\$(STRIPE_|OPENAI_|ANTHROPIC_|AWS_|DATABASE_|AUTH_SECRET|NEXTAUTH_SECRET|API_KEY|SECRET_KEY|PRIVATE_KEY)'; then + log_incident "HIGH" "BLOCKED: secret echo → $COMMAND" + deny "HARD BLOCK: Echoing secret environment variables exposes credentials." "Reference secrets by variable name only. Never echo their values." +fi + +# Block piping credential files to network commands (curl, wget, nc, etc.) +if echo "$COMMAND" | grep -qE '\.env.*\|\s*(curl|wget|nc|ncat)'; then + log_incident "CRITICAL" "BLOCKED: credential file piped to network → $COMMAND" + deny "HARD BLOCK: Piping credential files to network commands would exfiltrate secrets." "Never pipe .env files to network commands." +fi + +# Block git add of credential files +if echo "$COMMAND" | grep -qE 'git\s+add\s+.*(\.(env|env\.local|env\.production))'; then + log_incident "CRITICAL" "BLOCKED: git add of credential file → $COMMAND" + deny "HARD BLOCK: Staging credential files (.env) for git commit would expose secrets publicly." "These files must stay in .gitignore. Never commit credentials to git." +fi + +# ═══════════════════════════════════════════════════════ +# SOFT BLOCK — blocked, but user can re-request +# ═══════════════════════════════════════════════════════ + +# rm with -r or -f flags (recursive/force delete) +if echo "$COMMAND" | grep -qE 'rm\s+(-[a-zA-Z]*[rf][a-zA-Z]*\s+)'; then + # Allow rm on .claude/backups (rotation) and .claude/logs temp files + if echo "$COMMAND" | grep -qE '\.claude/(backups|logs/\.(quality-gate-active|session-blocks|tool-call-count|compaction-occurred))'; then + exit 0 + fi + log_incident "MEDIUM" "SOFT BLOCKED: recursive/force rm → $COMMAND" + deny "SOFT BLOCK: rm with -r or -f flags deletes files permanently." "Command blocked: recursive/force delete. If intentional, ask the user to confirm with specific file paths listed." +fi + +# Overwriting system/config files +if echo "$COMMAND" | grep -qE '>\s*(~\/\.|\/etc\/|\.env|\.ssh|\.claude\/settings)'; then + log_incident "HIGH" "SOFT BLOCKED: config/system file overwrite → $COMMAND" + deny "SOFT BLOCK: Writing to a sensitive config/system file." "Command blocked: system file overwrite detected. Verify this is intentional with the user." +fi + +# curl piped to shell (arbitrary code execution) +if echo "$COMMAND" | grep -qE 'curl\s.*\|\s*(bash|sh|zsh)'; then + log_incident "HIGH" "SOFT BLOCKED: curl pipe to shell → $COMMAND" + deny "SOFT BLOCK: Piping curl to a shell executes arbitrary remote code." "Command blocked: curl pipe to shell. Download the file first, inspect it, then run it." +fi + +# ═══════════════════════════════════════════════════════ +# LOG WARNING — allowed but recorded +# ═══════════════════════════════════════════════════════ + +# Any rm command (non-recursive, non-force) +if echo "$COMMAND" | grep -qE '\brm\b'; then + log_incident "LOW" "WARNING: rm command allowed → $COMMAND" +fi + +# Any mv command (could lose data if target exists) +if echo "$COMMAND" | grep -qE '\bmv\b'; then + log_incident "LOW" "WARNING: mv command allowed → $COMMAND" +fi + +# Any git checkout that discards changes +if echo "$COMMAND" | grep -qE 'git\s+checkout\s+\.'; then + log_incident "MEDIUM" "WARNING: git checkout . discards changes → $COMMAND" +fi + +# Writing to files outside project directory +if echo "$COMMAND" | grep -qE '>\s*/' | grep -qvE ">\s*$CLAUDE_PROJECT_DIR"; then + log_incident "MEDIUM" "WARNING: write outside project dir → $COMMAND" +fi + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/log-changes.sh b/clowdex-download/.claude/.claude/hooks/log-changes.sh new file mode 100755 index 0000000..53a7e4a --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/log-changes.sh @@ -0,0 +1,22 @@ +#!/bin/bash +# PostToolUse async hook — appends every Write|Edit to audit trail. +# Provides a chronological record of all file modifications. + +INPUT=$(cat) +FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty') +TOOL=$(echo "$INPUT" | jq -r '.tool_name // empty') +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +AUDIT_TRAIL="$LOG_DIR/audit-trail.md" + +mkdir -p "$LOG_DIR" + +# Skip if no file path +[ -z "$FILE_PATH" ] && exit 0 + +# Get relative path for cleaner logs +RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}" + +echo "- \`$TIMESTAMP\` | $TOOL | $RELATIVE_PATH" >> "$AUDIT_TRAIL" + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/log-failures.sh b/clowdex-download/.claude/.claude/hooks/log-failures.sh new file mode 100755 index 0000000..cb0d084 --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/log-failures.sh @@ -0,0 +1,57 @@ +#!/bin/bash +# PostToolUseFailure hook — categorizes and logs tool failures. +# Categories: BUILD, API, FILESYSTEM, NETWORK, PERMISSION, OTHER +# Severities: CRITICAL, ERROR, WARN, INFO + +INPUT=$(cat) +TOOL=$(echo "$INPUT" | jq -r '.tool_name // empty') +ERROR=$(echo "$INPUT" | jq -r '.error // .tool_result // empty' | head -5) +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +FAILURE_LOG="$LOG_DIR/failure-log.md" +INCIDENT_LOG="$LOG_DIR/incident-log.md" + +mkdir -p "$LOG_DIR" + +# Categorize the failure +CATEGORY="OTHER" +SEVERITY="ERROR" + +case "$ERROR" in + *"ENOENT"*|*"No such file"*|*"not found"*) + CATEGORY="FILESYSTEM" + SEVERITY="WARN" + ;; + *"EACCES"*|*"Permission denied"*|*"EPERM"*) + CATEGORY="PERMISSION" + SEVERITY="ERROR" + ;; + *"ECONNREFUSED"*|*"ETIMEDOUT"*|*"fetch failed"*|*"network"*) + CATEGORY="NETWORK" + SEVERITY="ERROR" + ;; + *"401"*|*"403"*|*"429"*|*"500"*|*"API"*|*"rate limit"*) + CATEGORY="API" + SEVERITY="ERROR" + ;; + *"build"*|*"compile"*|*"syntax"*|*"TypeError"*|*"ReferenceError"*) + CATEGORY="BUILD" + SEVERITY="ERROR" + ;; + *"CRITICAL"*|*"fatal"*|*"panic"*) + SEVERITY="CRITICAL" + ;; +esac + +# Truncate error for log readability +SHORT_ERROR=$(echo "$ERROR" | head -1 | cut -c1-200) + +# Write to failure log +echo "- \`$TIMESTAMP\` | $SEVERITY | $CATEGORY | $TOOL | $SHORT_ERROR" >> "$FAILURE_LOG" + +# Also write to incident log if ERROR or CRITICAL +if [ "$SEVERITY" = "ERROR" ] || [ "$SEVERITY" = "CRITICAL" ]; then + echo "- \`$TIMESTAMP\` | FAILURE | $SEVERITY | $CATEGORY | $TOOL | $SHORT_ERROR" >> "$INCIDENT_LOG" +fi + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/log-stop-verdict.sh b/clowdex-download/.claude/.claude/hooks/log-stop-verdict.sh new file mode 100755 index 0000000..382c85e --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/log-stop-verdict.sh @@ -0,0 +1,71 @@ +#!/bin/bash +# Stop hook — logs the quality verdict from the haiku review prompt. +# Writes structured JSONL for trend analysis across sessions. +# Tracks session blocks and activates quality gate at >=2 blocks. + +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +VERDICT_LOG="$LOG_DIR/verdicts.jsonl" +INCIDENT_LOG="$LOG_DIR/incident-log.md" +NOMINATIONS="$CLAUDE_PROJECT_DIR/.claude/knowledge-nominations.md" +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +SESSION_DATE=$(date +"%m%d-%H") +BLOCK_FILE="$LOG_DIR/.session-blocks-$SESSION_DATE" + +mkdir -p "$LOG_DIR" + +# Read the verdict from stdin (piped from the Stop prompt) +RAW_VERDICT=$(cat) + +# Strip markdown code fences and prose that Haiku sometimes adds +VERDICT=$(echo "$RAW_VERDICT" | sed -n '/^{/,/^}/p' | head -1) +# Fallback: try the raw input if sed extraction failed +if [ -z "$VERDICT" ]; then + VERDICT="$RAW_VERDICT" +fi + +# Try to parse as JSON +DECISION=$(echo "$VERDICT" | jq -r '.decision // empty' 2>/dev/null) +LEARNING=$(echo "$VERDICT" | jq -r '.learning // empty' 2>/dev/null) +TASK_TYPE=$(echo "$VERDICT" | jq -r '.task_type // "other"' 2>/dev/null) +REASON=$(echo "$VERDICT" | jq -r '.reason // empty' 2>/dev/null) + +# Default if not parseable +if [ -z "$DECISION" ]; then + DECISION="unknown" + TASK_TYPE="other" +fi + +# Write JSONL verdict +jq -n \ + --arg ts "$TIMESTAMP" \ + --arg decision "$DECISION" \ + --arg learning "$LEARNING" \ + --arg task_type "$TASK_TYPE" \ + --arg reason "$REASON" \ + '{timestamp: $ts, decision: $decision, learning: $learning, task_type: $task_type, reason: $reason}' \ + >> "$VERDICT_LOG" + +# Track blocks +if [ "$DECISION" = "block" ]; then + BLOCK_COUNT=1 + if [ -f "$BLOCK_FILE" ]; then + BLOCK_COUNT=$(( $(cat "$BLOCK_FILE") + 1 )) + fi + echo "$BLOCK_COUNT" > "$BLOCK_FILE" + + echo "- \`$TIMESTAMP\` | VERDICT | BLOCK | $REASON" >> "$INCIDENT_LOG" + + # Activate quality gate at >=2 blocks in same session + if [ "$BLOCK_COUNT" -ge 2 ]; then + touch "$LOG_DIR/.quality-gate-active" + echo "- \`$TIMESTAMP\` | VERDICT | WARN | Quality gate activated — $BLOCK_COUNT blocks this session" >> "$INCIDENT_LOG" + fi +fi + +# Nominate learning if present +if [ -n "$LEARNING" ] && [ "$LEARNING" != "null" ]; then + NOMINATION_DATE=$(date +"%m%d%y") + echo "- [$NOMINATION_DATE] stop-hook: $LEARNING | Evidence: session verdict ($TASK_TYPE)" >> "$NOMINATIONS" +fi + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/post-compact-resume.sh b/clowdex-download/.claude/.claude/hooks/post-compact-resume.sh new file mode 100755 index 0000000..e36d35f --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/post-compact-resume.sh @@ -0,0 +1,26 @@ +#!/bin/bash +# SessionStart(compact) hook — restores context after auto-compaction. +# Reads the marker left by pre-compact-handoff.sh, resets counters, +# and injects resumption instructions for Claude. + +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +MARKER="$LOG_DIR/.compaction-occurred" + +# Only run if compaction actually occurred +if [ ! -f "$MARKER" ]; then + exit 0 +fi + +# Reset session counters +rm -f "$LOG_DIR/.tool-call-count" "$LOG_DIR/.quality-gate-active" 2>/dev/null + +# Read compaction timestamp +COMPACT_TIME=$(cat "$MARKER" 2>/dev/null || echo "unknown") + +# Clean up marker +rm -f "$MARKER" + +# Output resumption context for Claude +echo "POST-COMPACTION RESUME: Context was auto-compacted at $COMPACT_TIME. Session state was preserved in memory.md and daily note. Read .claude/memory.md and the latest Daily Note (look for the latest Session Handoff) to reload context, then continue working on whatever task was in progress. Do not ask the user what to do — just resume seamlessly." + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/pre-compact-handoff.sh b/clowdex-download/.claude/.claude/hooks/pre-compact-handoff.sh new file mode 100755 index 0000000..b60dbc0 --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/pre-compact-handoff.sh @@ -0,0 +1,14 @@ +#!/bin/bash +# PreCompact hook — saves a marker before auto-compaction. +# The post-compact-resume.sh hook reads this marker to restore context. + +TIMESTAMP=$(date +"%Y-%m-%d %H:%M:%S") +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +INCIDENT_LOG="$LOG_DIR/incident-log.md" + +mkdir -p "$LOG_DIR" + +echo "$TIMESTAMP" > "$LOG_DIR/.compaction-occurred" +echo "- \`$TIMESTAMP\` | COMPACTION | INFO | Auto-compaction triggered — state saved" >> "$INCIDENT_LOG" + +exit 0 diff --git a/clowdex-download/.claude/.claude/hooks/session-reset.sh b/clowdex-download/.claude/.claude/hooks/session-reset.sh new file mode 100755 index 0000000..8780882 --- /dev/null +++ b/clowdex-download/.claude/.claude/hooks/session-reset.sh @@ -0,0 +1,79 @@ +#!/bin/bash +# SessionStart(user) hook — resets stale state on fresh session start. +# Cleans up gate files, validates agent definitions, checks permissions. + +LOG_DIR="$CLAUDE_PROJECT_DIR/.claude/logs" +AGENTS_DIR="$CLAUDE_PROJECT_DIR/.claude/agents" +HOOKS_DIR="$CLAUDE_PROJECT_DIR/.claude/hooks" + +mkdir -p "$LOG_DIR" + +# ═══════════════════════════════════════════════════════ +# 1. Reset stale gate files (prevents cross-session deadlocks) +# ═══════════════════════════════════════════════════════ +rm -f "$LOG_DIR/.quality-gate-active" \ + "$LOG_DIR/.tool-call-count" \ + "$LOG_DIR/.compaction-occurred" 2>/dev/null + +# Clean up stale session-blocks files (older than current hour) +find "$LOG_DIR" -name ".session-blocks-*" -mmin +120 -delete 2>/dev/null + +# ═══════════════════════════════════════════════════════ +# 2. Validate hook scripts are executable +# ═══════════════════════════════════════════════════════ +if [ -d "$HOOKS_DIR" ]; then + HOOK_ISSUES=0 + for hook in "$HOOKS_DIR"/*.sh; do + [ ! -f "$hook" ] && continue + if [ ! -x "$hook" ]; then + chmod +x "$hook" 2>/dev/null + HOOK_ISSUES=$((HOOK_ISSUES + 1)) + fi + done + if [ "$HOOK_ISSUES" -gt 0 ]; then + echo "- \`$(date +"%Y-%m-%d %H:%M:%S")\` | SESSION | INFO | Fixed permissions on $HOOK_ISSUES hook scripts" >> "$LOG_DIR/incident-log.md" + fi +fi + +# ═══════════════════════════════════════════════════════ +# 3. Validate agent definitions exist and have frontmatter +# ═══════════════════════════════════════════════════════ +if [ -d "$AGENTS_DIR" ]; then + AGENT_ISSUES="" + for agent in "$AGENTS_DIR"/*.md; do + [ ! -f "$agent" ] && continue + AGENT_NAME=$(basename "$agent" .md) + + # Check for frontmatter (starts with ---) + if ! head -1 "$agent" | grep -q '^---'; then + AGENT_ISSUES="$AGENT_ISSUES $AGENT_NAME(no-frontmatter)" + fi + done + + if [ -n "$AGENT_ISSUES" ]; then + echo "- \`$(date +"%Y-%m-%d %H:%M:%S")\` | SESSION | WARN | Agent issues:$AGENT_ISSUES" >> "$LOG_DIR/incident-log.md" + fi +fi + +# ═══════════════════════════════════════════════════════ +# 4. Ensure required directories exist +# ═══════════════════════════════════════════════════════ +mkdir -p "$CLAUDE_PROJECT_DIR/.claude/agent-memory" \ + "$CLAUDE_PROJECT_DIR/.claude/backups" \ + "$CLAUDE_PROJECT_DIR/.claude/skills" \ + "$CLAUDE_PROJECT_DIR/Daily Notes" 2>/dev/null + +# ═══════════════════════════════════════════════════════ +# 5. Prune old log files (keep last 30 days) +# ═══════════════════════════════════════════════════════ +if [ -f "$LOG_DIR/audit-trail.md" ]; then + LINE_COUNT=$(wc -l < "$LOG_DIR/audit-trail.md" | tr -d ' ') + if [ "$LINE_COUNT" -gt 5000 ]; then + # Keep last 2000 lines + tail -2000 "$LOG_DIR/audit-trail.md" > "$LOG_DIR/audit-trail.md.tmp" + mv "$LOG_DIR/audit-trail.md.tmp" "$LOG_DIR/audit-trail.md" + echo "- \`$(date +"%Y-%m-%d %H:%M:%S")\` | SESSION | INFO | Pruned audit trail from $LINE_COUNT to 2000 lines" >> "$LOG_DIR/incident-log.md" + fi +fi + +exit 0 diff --git a/clowdex-download/.claude/.claude/knowledge-base.md b/clowdex-download/.claude/.claude/knowledge-base.md new file mode 100644 index 0000000..07ad90b --- /dev/null +++ b/clowdex-download/.claude/.claude/knowledge-base.md @@ -0,0 +1,23 @@ +# Knowledge Base + +System-wide learned rules. Read by ALL agents and sessions at startup. +Written ONLY by the sentinel after confirming learnings. +Entries are mandatory constraints, not suggestions. + +## Source Priority +Every entry MUST cite its source using one of: +- `[Source: user override MMDDYY]` — User explicitly corrected something +- `[Source: empirical MMDDYY]` — Verified through testing or data +- `[Source: agent inference MMDDYY]` — Pattern observed by an agent, confirmed by sentinel + +## Hard Rules +- (none yet — rules accumulate as you work and the sentinel validates learnings) + +## Platform & Tool Rules +- (none yet) + +## Project Patterns +- (none yet) + +## Known Failure Modes +- (none yet) diff --git a/clowdex-download/.claude/.claude/knowledge-nominations.md b/clowdex-download/.claude/.claude/knowledge-nominations.md new file mode 100644 index 0000000..9c8642e --- /dev/null +++ b/clowdex-download/.claude/.claude/knowledge-nominations.md @@ -0,0 +1,6 @@ +# Knowledge Nominations + +Candidate learnings from agents and sessions. The sentinel reviews these +during each audit cycle and promotes valid ones to knowledge-base.md. + +## Pending Nominations diff --git a/clowdex-download/.claude/.claude/memory.md b/clowdex-download/.claude/.claude/memory.md new file mode 100644 index 0000000..0803144 --- /dev/null +++ b/clowdex-download/.claude/.claude/memory.md @@ -0,0 +1,13 @@ +# Memory + +## Now +- Starting new project with Clowdex + +## Open Threads +- (none yet) + +## Recent Decisions +- (none yet) + +## Blockers +- (none) diff --git a/clowdex-download/.claude/.claude/settings.json b/clowdex-download/.claude/.claude/settings.json new file mode 100644 index 0000000..eff047f --- /dev/null +++ b/clowdex-download/.claude/.claude/settings.json @@ -0,0 +1,115 @@ +{ + "$schema": "https://json.schemastore.org/claude-code-settings.json", + "hooks": { + "PreToolUse": [ + { + "matcher": "Bash", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/guard-bash.sh\"", + "statusMessage": "Checking command safety..." + } + ] + }, + { + "matcher": "Write|Edit|NotebookEdit", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/backup-before-write.sh\"", + "statusMessage": "Backing up before write...", + "async": true + }, + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/completeness-gate.sh\"", + "statusMessage": "Validating content completeness...", + "async": false + } + ] + } + ], + "PostToolUse": [ + { + "matcher": "Write|Edit|NotebookEdit", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/log-changes.sh\"", + "statusMessage": "Logging change...", + "async": true + } + ] + } + ], + "PostToolUseFailure": [ + { + "matcher": "*", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/log-failures.sh\"", + "statusMessage": "Logging failure...", + "async": true + } + ] + } + ], + "PreCompact": [ + { + "matcher": "auto", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/pre-compact-handoff.sh\"", + "timeout": 5, + "statusMessage": "Saving state before compaction..." + } + ] + } + ], + "SessionStart": [ + { + "matcher": "user", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/session-reset.sh\"", + "timeout": 3, + "statusMessage": "Resetting session state..." + } + ] + }, + { + "matcher": "compact", + "hooks": [ + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/post-compact-resume.sh\"", + "timeout": 10, + "statusMessage": "Restoring context after compaction..." + } + ] + } + ], + "Stop": [ + { + "hooks": [ + { + "type": "prompt", + "prompt": "You are a JSON-only response bot. Output raw JSON with no markdown, no code fences, no prose. Review this conversation and return exactly one JSON object: {\"decision\":\"allow\",\"learning\":null,\"task_type\":\"other\"} — decision is \"allow\" if all user-requested tasks were completed, \"block\" if something was missed (add \"reason\" field). learning is a one-sentence lesson if errors were resolved (root cause + fix), otherwise null. task_type is one of: build, debug, refactor, test, docs, research, deploy, admin, setup, other. RESPOND WITH ONLY THE JSON OBJECT. NO OTHER TEXT.", + "timeout": 15, + "model": "haiku" + }, + { + "type": "command", + "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/log-stop-verdict.sh\"", + "statusMessage": "Logging session verdict...", + "async": true + } + ] + } + ] + } +} diff --git a/clowdex-download/.claude/.claude/skills/INDEX.md b/clowdex-download/.claude/.claude/skills/INDEX.md new file mode 100644 index 0000000..e54c7f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/INDEX.md @@ -0,0 +1,68 @@ +# Clowdex Skill-Bibliothek + +> 1.792 professionelle Skills in 32 Kategorien. +> Jeder Skill ist eine strukturierte Arbeitsanleitung — kein einfaches Prompt-Template. + +## So funktionieren Skills + +Skills werden automatisch aktiviert, wenn Claude eine passende Aufgabe erkennt, oder manuell über `/skill-name`. +Jeder Skill: +- Liest den Projektkontext aus `memory.md` und `knowledge-base.md` +- Folgt einem strukturierten Prozess mit benannten Frameworks +- Erzeugt ein definiertes Ausgabeformat +- Prüft die Qualität vor der Auslieferung +- Aktualisiert den Projekt-Memory mit Erkenntnissen + +## Kategorien + +| Kategorie | Skills | Beschreibung | +|-----------|--------|-------------| +| [Marketing & Advertising](./marketing/) | 76 | Kampagnenstrategie, Zielgruppenanalyse, Markenpositionierung und Werbung über alle Kanäle | +| [Content & Copywriting](./content/) | 88 | Texterstellung in allen Formaten — Blogposts, Whitepaper, Landingpages, Skripte und mehr | +| [Social Media](./social-media/) | 69 | Plattformspezifische Inhalte, Planung, Engagement und Analytics für alle großen Plattformen | +| [SEO & Search](./seo/) | 57 | Suchmaschinenoptimierung — Keyword-Recherche, On-Page, Technik, Linkaufbau, lokale SEO und Analytics | +| [Sales & Revenue](./sales/) | 66 | Vertriebsstrategie, Akquise, Outreach, Verhandlung, Pipeline-Management und Revenue Operations | +| [Email Marketing](./email/) | 51 | E-Mail-Kampagnen, Automatisierung, Sequenzen, Zustellbarkeit und Abonnenten-Management | +| [Finance & Accounting](./finance/) | 60 | Finanzmodellierung, Budgetierung, Prognosen, Preisgestaltung und Finanzberichte | +| [Legal & Compliance](./legal/) | 54 | Verträge, Richtlinien, Compliance-Frameworks und rechtliche Dokumentation | +| [Operations & Project Management](./operations/) | 60 | Prozessdesign, Projektplanung, Ressourcenmanagement und operative Exzellenz | +| [HR & People](./hr/) | 57 | Recruiting, Onboarding, Performance Management, Kultur, Schulung und Mitarbeitererfahrung | +| [Product Management](./product/) | 63 | Produktstrategie, Roadmaps, Nutzerforschung, Priorisierung und Produkt-Operations | +| [Software Development](./development/) | 78 | Code-Qualität, Architektur, Testing, CI/CD, Dokumentation, Debugging und Engineering-Praktiken | +| [Data & Analytics](./data/) | 57 | Datenanalyse, Visualisierung, Reporting, BI-Dashboards und Datenstrategie | +| [E-commerce](./ecommerce/) | 54 | Online-Shop-Management, Produktlistings, Conversion-Optimierung und Marktplatzstrategie | +| [Customer Success & Support](./customer-success/) | 48 | Kunden-Onboarding, Retention, Support-Operations und Kundenerfahrung | +| [Startup & Entrepreneurship](./startup/) | 60 | Geschäftsplanung, Fundraising, Validierung, Wachstum und Startup-Operations | +| [Education & Training](./education/) | 51 | Kurserstellung, Lehrplandesign, Bewertung, Workshops und Lernmanagement | +| [Real Estate](./real-estate/) | 45 | Immobilienangebote, Marktanalyse, Investitionsanalyse und Immobilien-Operations | +| [Healthcare](./healthcare/) | 48 | Patientenkommunikation, Praxismanagement, Compliance, Wellness-Programme und Gesundheitsinhalte | +| [Travel & Hospitality](./travel/) | 54 | Reiseplanung, Hotellerie-Operations, Gästeerfahrung und Reise-Inhalte | +| [Design & Creative](./design/) | 54 | Design-Briefings, Markenidentität, UX/UI, Creative Direction und visuelle Designprozesse | +| [Consulting & Strategy](./consulting/) | 54 | Strategie-Frameworks, Marktanalyse, Kundenprojekte und Beratungsleistungen | +| [Personal Productivity](./productivity/) | 57 | Zeitmanagement, Zielsetzung, Entscheidungsfindung, Kommunikation und persönliche Effektivität | +| [Cybersecurity & Information Security](./cybersecurity/) | 54 | Penetrationstests, Bedrohungsanalyse, Sicherheitsarchitektur, Compliance (SOC 2, ISO 27001, NIST), Incident Response, SecOps und Datenschutz | +| [AI & Automation](./ai-automation/) | 65 | KI-Implementierung, Prompt Engineering, Workflow-Automatisierung, KI-Strategie, EU AI Act Compliance, LLM-Architektur, KI-Governance und Bias-Audits | +| [Nonprofit & Social Impact](./nonprofit/) | 48 | Fundraising, Förderanträge, Freiwilligenmanagement und gemeinnützige Operations | +| [Media & Publishing](./media/) | 45 | Content-Veröffentlichung, Redaktionsmanagement, Medienproduktion und Reichweitenaufbau | +| [Construction & Trades](./construction/) | 42 | Projektkalkulation, Arbeitssicherheit, Kundenmanagement und Handwerks-Operations | +| [Food & Beverage](./food-beverage/) | 42 | Gastronomie-Betrieb, Menügestaltung, Lebensmittelsicherheit und Hospitality-Management | +| [Fitness & Wellness](./fitness-wellness/) | 45 | Programmgestaltung, Kundenbetreuung, Wellness-Coaching und Fitness-Business-Operations | +| [Agriculture & Farming](./agriculture/) | 45 | Betriebsplanung, Anbaumanagement, Tierhaltung und landwirtschaftliche Geschäftsführung | +| [Energy & Sustainability](./energy/) | 45 | Energiemanagement, Nachhaltigkeitsberichte, Umwelt-Compliance und grüne Initiativen | + +## Schnellstart + +1. Starte einen Skill, indem du Claude bittest, die Aufgabe auszuführen (Skills werden automatisch erkannt) +2. Oder rufe direkt auf: „Nutze den [skill-name] Skill für..." +3. Skills lesen den Projektkontext automatisch +4. Die Ausgabe folgt einem strukturierten Format mit Qualitätsprüfungen +5. Erkenntnisse werden für zukünftige Verbesserungen festgehalten + +## Qualitätsstandard + +Jeder Skill in dieser Bibliothek erfüllt einen einheitlichen Qualitätsstandard: +- **Umsetzbar**: Jeder Schritt sagt Claude genau, was zu tun ist +- **Konkret**: Enthält spezifische Zahlen, Frameworks und Schwellenwerte +- **Vollständig**: Deckt den gesamten Workflow von Eingabe bis Ergebnis ab +- **Systemintegriert**: Arbeitet mit Memory, Wissensdatenbank und Prüfprotokoll zusammen +- **Validiert**: Enthält eine Qualitäts-Checkliste vor der Auslieferung diff --git a/clowdex-download/.claude/.claude/skills/agriculture/animal-welfare-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/animal-welfare-audit/SKILL.md new file mode 100644 index 0000000..5050fd7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/animal-welfare-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a animal welfare audit with structured process, quality checks, and system integration +--- + +# Animal Welfare Audit + +## Purpose + +Analyze and produce a comprehensive animal welfare audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing animal welfare audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the animal welfare audit +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the animal welfare audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Animal Welfare Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/breeding-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/breeding-plan/SKILL.md new file mode 100644 index 0000000..7b17a2d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/breeding-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a breeding plan with structured process, quality checks, and system integration +--- + +# Breeding Plan + +## Purpose + +Design and document a comprehensive breeding plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breeding plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breeding plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breeding plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Breeding Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/carbon-footprint/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/carbon-footprint/SKILL.md new file mode 100644 index 0000000..2fa9a4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/carbon-footprint/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a carbon footprint with structured process, quality checks, and system integration +--- + +# Carbon Footprint + +## Purpose + +Create a comprehensive carbon footprint that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing carbon footprint documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the carbon footprint +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the carbon footprint using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Carbon Footprint + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/conservation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/conservation-plan/SKILL.md new file mode 100644 index 0000000..c6e267e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/conservation-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a conservation plan with structured process, quality checks, and system integration +--- + +# Conservation Plan + +## Purpose + +Design and document a comprehensive conservation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conservation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conservation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conservation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Conservation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/cost-per-acre/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/cost-per-acre/SKILL.md new file mode 100644 index 0000000..57838f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/cost-per-acre/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cost per acre with structured process, quality checks, and system integration +--- + +# Cost Per Acre + +## Purpose + +Create a comprehensive cost per acre that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost per acre documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost per acre +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost per acre using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Cost Per Acre + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/crop-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/crop-plan/SKILL.md new file mode 100644 index 0000000..2a7c564 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/crop-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a crop plan with structured process, quality checks, and system integration +--- + +# Crop Plan + +## Purpose + +Design and document a comprehensive crop plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crop plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crop plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crop plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Crop Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/csa-program/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/csa-program/SKILL.md new file mode 100644 index 0000000..6360336 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/csa-program/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a csa program with structured process, quality checks, and system integration +--- + +# Csa Program + +## Purpose + +Design and document a comprehensive csa program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing csa program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the csa program +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the csa program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Csa Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/direct-to-consumer/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/direct-to-consumer/SKILL.md new file mode 100644 index 0000000..6a5768d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/direct-to-consumer/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a direct to consumer with structured process, quality checks, and system integration +--- + +# Direct To Consumer + +## Purpose + +Create a comprehensive direct to consumer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing direct to consumer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the direct to consumer +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the direct to consumer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Direct To Consumer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/disaster-preparedness-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/disaster-preparedness-farm/SKILL.md new file mode 100644 index 0000000..88b4b02 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/disaster-preparedness-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a disaster preparedness farm with structured process, quality checks, and system integration +--- + +# Disaster Preparedness Farm + +## Purpose + +Create a comprehensive disaster preparedness farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing disaster preparedness farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the disaster preparedness farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the disaster preparedness farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Disaster Preparedness Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/equipment-maintenance-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/equipment-maintenance-farm/SKILL.md new file mode 100644 index 0000000..0ae7be1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/equipment-maintenance-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a equipment maintenance farm with structured process, quality checks, and system integration +--- + +# Equipment Maintenance Farm + +## Purpose + +Create a comprehensive equipment maintenance farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing equipment maintenance farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the equipment maintenance farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the equipment maintenance farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Equipment Maintenance Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/equipment-roi/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/equipment-roi/SKILL.md new file mode 100644 index 0000000..4eeb18e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/equipment-roi/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a equipment roi with structured process, quality checks, and system integration +--- + +# Equipment Roi + +## Purpose + +Create a comprehensive equipment roi that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing equipment roi documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the equipment roi +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the equipment roi using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Equipment Roi + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/farm-budget/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/farm-budget/SKILL.md new file mode 100644 index 0000000..91b2e2f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/farm-budget/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a farm budget with structured process, quality checks, and system integration +--- + +# Farm Budget + +## Purpose + +Create a comprehensive farm budget that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing farm budget documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the farm budget +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the farm budget using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Farm Budget + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/farm-business-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/farm-business-plan/SKILL.md new file mode 100644 index 0000000..21fb245 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/farm-business-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a farm business plan with structured process, quality checks, and system integration +--- + +# Farm Business Plan + +## Purpose + +Design and document a comprehensive farm business plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing farm business plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the farm business plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the farm business plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Farm Business Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/farm-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/farm-marketing/SKILL.md new file mode 100644 index 0000000..4f7d5be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/farm-marketing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a farm marketing with structured process, quality checks, and system integration +--- + +# Farm Marketing + +## Purpose + +Create a comprehensive farm marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing farm marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the farm marketing +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the farm marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Farm Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/farmers-market-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/farmers-market-plan/SKILL.md new file mode 100644 index 0000000..a033a97 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/farmers-market-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a farmers market plan with structured process, quality checks, and system integration +--- + +# Farmers Market Plan + +## Purpose + +Design and document a comprehensive farmers market plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing farmers market plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the farmers market plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the farmers market plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Farmers Market Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/feed-management/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/feed-management/SKILL.md new file mode 100644 index 0000000..3e46961 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/feed-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a feed management with structured process, quality checks, and system integration +--- + +# Feed Management + +## Purpose + +Create a comprehensive feed management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feed management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feed management +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feed management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Feed Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/fertilizer-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/fertilizer-plan/SKILL.md new file mode 100644 index 0000000..7caf8eb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/fertilizer-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a fertilizer plan with structured process, quality checks, and system integration +--- + +# Fertilizer Plan + +## Purpose + +Design and document a comprehensive fertilizer plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fertilizer plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fertilizer plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fertilizer plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Fertilizer Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/grant-application-agriculture/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/grant-application-agriculture/SKILL.md new file mode 100644 index 0000000..2d85294 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/grant-application-agriculture/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a grant application agriculture with structured process, quality checks, and system integration +--- + +# Grant Application Agriculture + +## Purpose + +Create a comprehensive grant application agriculture that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grant application agriculture documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grant application agriculture +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grant application agriculture using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Grant Application Agriculture + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/harvest-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/harvest-plan/SKILL.md new file mode 100644 index 0000000..cc3ed54 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/harvest-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a harvest plan with structured process, quality checks, and system integration +--- + +# Harvest Plan + +## Purpose + +Design and document a comprehensive harvest plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing harvest plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the harvest plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the harvest plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Harvest Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/health-protocol-livestock/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/health-protocol-livestock/SKILL.md new file mode 100644 index 0000000..e22bcbd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/health-protocol-livestock/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a health protocol livestock with structured process, quality checks, and system integration +--- + +# Health Protocol Livestock + +## Purpose + +Create a comprehensive health protocol livestock that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing health protocol livestock documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the health protocol livestock +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the health protocol livestock using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Health Protocol Livestock + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/insurance-review-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/insurance-review-farm/SKILL.md new file mode 100644 index 0000000..55e23e5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/insurance-review-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a insurance review farm with structured process, quality checks, and system integration +--- + +# Insurance Review Farm + +## Purpose + +Analyze and produce a comprehensive insurance review farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing insurance review farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the insurance review farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the insurance review farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Insurance Review Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/integrated-pest-management/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/integrated-pest-management/SKILL.md new file mode 100644 index 0000000..4b1da25 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/integrated-pest-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a integrated pest management with structured process, quality checks, and system integration +--- + +# Integrated Pest Management + +## Purpose + +Create a comprehensive integrated pest management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing integrated pest management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the integrated pest management +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the integrated pest management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Integrated Pest Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/irrigation-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/irrigation-schedule/SKILL.md new file mode 100644 index 0000000..abdbf81 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/irrigation-schedule/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a irrigation schedule with structured process, quality checks, and system integration +--- + +# Irrigation Schedule + +## Purpose + +Design and document a comprehensive irrigation schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing irrigation schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the irrigation schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the irrigation schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Irrigation Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/labor-management-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/labor-management-farm/SKILL.md new file mode 100644 index 0000000..f561c03 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/labor-management-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a labor management farm with structured process, quality checks, and system integration +--- + +# Labor Management Farm + +## Purpose + +Create a comprehensive labor management farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing labor management farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the labor management farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the labor management farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Labor Management Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/land-acquisition/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/land-acquisition/SKILL.md new file mode 100644 index 0000000..dc718db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/land-acquisition/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a land acquisition with structured process, quality checks, and system integration +--- + +# Land Acquisition + +## Purpose + +Create a comprehensive land acquisition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing land acquisition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the land acquisition +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the land acquisition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Land Acquisition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/lease-negotiation-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/lease-negotiation-farm/SKILL.md new file mode 100644 index 0000000..2ff3f78 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/lease-negotiation-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a lease negotiation farm with structured process, quality checks, and system integration +--- + +# Lease Negotiation Farm + +## Purpose + +Create a comprehensive lease negotiation farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lease negotiation farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lease negotiation farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lease negotiation farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Lease Negotiation Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/livestock-management/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/livestock-management/SKILL.md new file mode 100644 index 0000000..8c0c439 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/livestock-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a livestock management with structured process, quality checks, and system integration +--- + +# Livestock Management + +## Purpose + +Create a comprehensive livestock management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing livestock management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the livestock management +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the livestock management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Livestock Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/organic-certification/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/organic-certification/SKILL.md new file mode 100644 index 0000000..04e2701 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/organic-certification/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a organic certification with structured process, quality checks, and system integration +--- + +# Organic Certification + +## Purpose + +Create a comprehensive organic certification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing organic certification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the organic certification +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the organic certification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Organic Certification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/pasture-rotation/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/pasture-rotation/SKILL.md new file mode 100644 index 0000000..afeeadf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/pasture-rotation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a pasture rotation with structured process, quality checks, and system integration +--- + +# Pasture Rotation + +## Purpose + +Create a comprehensive pasture rotation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pasture rotation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pasture rotation +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pasture rotation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Pasture Rotation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/pest-management/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/pest-management/SKILL.md new file mode 100644 index 0000000..57a984c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/pest-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a pest management with structured process, quality checks, and system integration +--- + +# Pest Management + +## Purpose + +Create a comprehensive pest management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pest management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pest management +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pest management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Pest Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/planting-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/planting-schedule/SKILL.md new file mode 100644 index 0000000..0ba3ca3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/planting-schedule/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a planting schedule with structured process, quality checks, and system integration +--- + +# Planting Schedule + +## Purpose + +Design and document a comprehensive planting schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing planting schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the planting schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the planting schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Planting Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/post-harvest-handling/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/post-harvest-handling/SKILL.md new file mode 100644 index 0000000..592160d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/post-harvest-handling/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a post harvest handling with structured process, quality checks, and system integration +--- + +# Post Harvest Handling + +## Purpose + +Create a comprehensive post harvest handling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing post harvest handling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the post harvest handling +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the post harvest handling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Post Harvest Handling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/profit-analysis-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/profit-analysis-farm/SKILL.md new file mode 100644 index 0000000..318d439 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/profit-analysis-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a profit analysis farm with structured process, quality checks, and system integration +--- + +# Profit Analysis Farm + +## Purpose + +Analyze and produce a comprehensive profit analysis farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing profit analysis farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the profit analysis farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the profit analysis farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Profit Analysis Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/regenerative-practices/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/regenerative-practices/SKILL.md new file mode 100644 index 0000000..24a978d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/regenerative-practices/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a regenerative practices with structured process, quality checks, and system integration +--- + +# Regenerative Practices + +## Purpose + +Create a comprehensive regenerative practices that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing regenerative practices documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the regenerative practices +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the regenerative practices using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Regenerative Practices + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/seasonal-hiring/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/seasonal-hiring/SKILL.md new file mode 100644 index 0000000..e65b7a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/seasonal-hiring/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a seasonal hiring with structured process, quality checks, and system integration +--- + +# Seasonal Hiring + +## Purpose + +Create a comprehensive seasonal hiring that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seasonal hiring documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seasonal hiring +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seasonal hiring using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Seasonal Hiring + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/soil-analysis-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/soil-analysis-plan/SKILL.md new file mode 100644 index 0000000..b637ffd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/soil-analysis-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a soil analysis plan with structured process, quality checks, and system integration +--- + +# Soil Analysis Plan + +## Purpose + +Analyze and produce a comprehensive soil analysis plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soil analysis plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soil analysis plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soil analysis plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Soil Analysis Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/storage-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/storage-plan/SKILL.md new file mode 100644 index 0000000..12b90fd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/storage-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a storage plan with structured process, quality checks, and system integration +--- + +# Storage Plan + +## Purpose + +Design and document a comprehensive storage plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing storage plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the storage plan +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the storage plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Storage Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/subsidy-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/subsidy-tracker/SKILL.md new file mode 100644 index 0000000..0d66487 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/subsidy-tracker/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a subsidy tracker with structured process, quality checks, and system integration +--- + +# Subsidy Tracker + +## Purpose + +Analyze and produce a comprehensive subsidy tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subsidy tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subsidy tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subsidy tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Subsidy Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/succession-planning-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/succession-planning-farm/SKILL.md new file mode 100644 index 0000000..f790fec --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/succession-planning-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a succession planning farm with structured process, quality checks, and system integration +--- + +# Succession Planning Farm + +## Purpose + +Design and document a comprehensive succession planning farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing succession planning farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the succession planning farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the succession planning farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Succession Planning Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/sustainability-report-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/sustainability-report-farm/SKILL.md new file mode 100644 index 0000000..ac665bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/sustainability-report-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a sustainability report farm with structured process, quality checks, and system integration +--- + +# Sustainability Report Farm + +## Purpose + +Analyze and produce a comprehensive sustainability report farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainability report farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainability report farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainability report farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Sustainability Report Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/technology-adoption/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/technology-adoption/SKILL.md new file mode 100644 index 0000000..c7cb7b4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/technology-adoption/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a technology adoption with structured process, quality checks, and system integration +--- + +# Technology Adoption + +## Purpose + +Create a comprehensive technology adoption that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technology adoption documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technology adoption +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technology adoption using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Technology Adoption + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/value-added-product/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/value-added-product/SKILL.md new file mode 100644 index 0000000..6e933b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/value-added-product/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a value added product with structured process, quality checks, and system integration +--- + +# Value Added Product + +## Purpose + +Create a comprehensive value added product that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing value added product documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the value added product +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the value added product using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Value Added Product + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/weather-contingency/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/weather-contingency/SKILL.md new file mode 100644 index 0000000..2482760 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/weather-contingency/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a weather contingency with structured process, quality checks, and system integration +--- + +# Weather Contingency + +## Purpose + +Create a comprehensive weather contingency that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing weather contingency documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the weather contingency +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the weather contingency using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Weather Contingency + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/wholesale-channel/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/wholesale-channel/SKILL.md new file mode 100644 index 0000000..e698b5d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/wholesale-channel/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a wholesale channel with structured process, quality checks, and system integration +--- + +# Wholesale Channel + +## Purpose + +Create a comprehensive wholesale channel that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wholesale channel documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wholesale channel +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wholesale channel using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Wholesale Channel + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/agriculture/worker-safety-farm/SKILL.md b/clowdex-download/.claude/.claude/skills/agriculture/worker-safety-farm/SKILL.md new file mode 100644 index 0000000..40b1153 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/agriculture/worker-safety-farm/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a worker safety farm with structured process, quality checks, and system integration +--- + +# Worker Safety Farm + +## Purpose + +Create a comprehensive worker safety farm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Agriculture & Farming + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing worker safety farm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Integrated Pest Management (IPM), Regenerative Agriculture, Precision Agriculture + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the worker safety farm +- Identify gaps, opportunities, and risks +- Define success metrics: Yield Per Acre, Cost Per Unit Produced, Soil Health Score, Water Use Efficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the worker safety farm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Soil test annually before planting + +## Output Format + +```markdown +# Worker Safety Farm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Integrated Pest Management (IPM) +- Regenerative Agriculture +- Precision Agriculture +- Farm Financial Benchmarking +- Good Agricultural Practices (GAP) + +## Key Metrics +- Yield Per Acre +- Cost Per Unit Produced +- Soil Health Score +- Water Use Efficiency +- Input Cost Ratio +- Net Farm Income + +## Best Practices +- Soil test annually before planting +- Crop rotation minimum 3-year cycle +- Records for every field, every season +- Market before you plant — know your buyer +- Invest in soil health for long-term yields + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/agent-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/agent-evaluation/SKILL.md new file mode 100644 index 0000000..f535abf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/agent-evaluation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a agent evaluation with structured process, quality checks, and system integration +--- + +# Agent Evaluation + +## Purpose + +Analyze and produce a comprehensive agent evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing agent evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the agent evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the agent evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Agent Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-adoption-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-adoption-plan/SKILL.md new file mode 100644 index 0000000..bb38812 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-adoption-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai adoption plan with structured process, quality checks, and system integration +--- + +# Ai Adoption Plan + +## Purpose + +Design and document a comprehensive ai adoption plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai adoption plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai adoption plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai adoption plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Adoption Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-agent-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-agent-design/SKILL.md new file mode 100644 index 0000000..c3d8387 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-agent-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai agent design with structured process, quality checks, and system integration +--- + +# Ai Agent Design + +## Purpose + +Create a comprehensive ai agent design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai agent design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai agent design +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai agent design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Agent Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-assistant-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-assistant-spec/SKILL.md new file mode 100644 index 0000000..0612825 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-assistant-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai assistant spec with structured process, quality checks, and system integration +--- + +# Ai Assistant Spec + +## Purpose + +Create a comprehensive ai assistant spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai assistant spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai assistant spec +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai assistant spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Assistant Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-bias-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-bias-audit/SKILL.md new file mode 100644 index 0000000..a5c3164 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-bias-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai bias audit with structured process, quality checks, and system integration +--- + +# AI Bias Audit + +## Purpose + +Create a comprehensive ai bias audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai bias audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NYC Local Law 144, Fairness Metrics Suite, Disparate Impact Analysis (4/5ths Rule) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai bias audit +- Identify gaps, opportunities, and risks +- Define success metrics: Disparate Impact Ratio per Protected Class, Demographic Parity Difference, Equalized Odds Difference, Calibration Gap +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai bias audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Audit across all legally protected characteristics — regulations vary by jurisdiction + +## Output Format + +```markdown +# AI Bias Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NYC Local Law 144 (AEDT Bias Audits) +- Fairness Metrics Suite (Demographic Parity, Equalized Odds, Calibration) +- Disparate Impact Analysis (4/5ths Rule) +- NIST AI 100-2e2023 +- ISO/IEC TR 24027 + +## Key Metrics +- Disparate Impact Ratio per Protected Class +- Demographic Parity Difference +- Equalized Odds Difference +- Calibration Gap +- Bias Remediation Effectiveness +- Protected Class Coverage + +## Best Practices +- Audit across all legally protected characteristics — regulations vary by jurisdiction +- Use multiple fairness metrics — they are mathematically incompatible +- Audit the full pipeline (data, features, model, deployment), not just the final model +- Publish audit results with methodology transparency +- Build remediation into the audit cycle with re-audit verification + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-change-management/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-change-management/SKILL.md new file mode 100644 index 0000000..221cfe6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-change-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai change management with structured process, quality checks, and system integration +--- + +# Ai Change Management + +## Purpose + +Create a comprehensive ai change management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai change management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai change management +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai change management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Change Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-code-review/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-code-review/SKILL.md new file mode 100644 index 0000000..a81f47b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-code-review/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a ai code review with structured process, quality checks, and system integration +--- + +# Ai Code Review + +## Purpose + +Analyze and produce a comprehensive ai code review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai code review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai code review +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai code review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Code Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-compliance-documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-compliance-documentation/SKILL.md new file mode 100644 index 0000000..93f6f8a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-compliance-documentation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai compliance documentation with structured process, quality checks, and system integration +--- + +# AI Compliance Documentation + +## Purpose + +Create a comprehensive ai compliance documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai compliance documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: EU AI Act, China AI Regulatory Stack, US State-Level Laws + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai compliance documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Jurisdiction Coverage %, Documentation Completeness per Regulation, Regulatory Change Detection Time, Cross-Jurisdictional Conflict Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai compliance documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Build a jurisdiction-regulation matrix, not a single compliance document + +## Output Format + +```markdown +# AI Compliance Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- EU AI Act (2024/1689) +- China AI Regulatory Stack (Algorithm + Deep Synthesis + GenAI + Labeling) +- US State-Level Laws (~700 bills) +- Brazil AI Framework +- OECD AI Principles + +## Key Metrics +- Jurisdiction Coverage (%) +- Documentation Completeness per Regulation +- Regulatory Change Detection Time +- Cross-Jurisdictional Conflict Count +- Audit Readiness Score per Jurisdiction +- Requirement Traceability Coverage + +## Best Practices +- Build a jurisdiction-regulation matrix, not a single compliance document +- Track China regulations separately — they move fastest +- Monitor US state legislation quarterly (~700 bills in 2024) +- Maintain requirement traceability from regulation to implementation +- Plan for regulatory convergence toward risk-based models + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-pipeline/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-pipeline/SKILL.md new file mode 100644 index 0000000..6ad6102 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-pipeline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai content pipeline with structured process, quality checks, and system integration +--- + +# Ai Content Pipeline + +## Purpose + +Design and document a comprehensive ai content pipeline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai content pipeline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai content pipeline +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai content pipeline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Content Pipeline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-policy-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-policy-framework/SKILL.md new file mode 100644 index 0000000..7d6f105 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-content-policy-framework/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai content policy framework with structured process, quality checks, and system integration +--- + +# AI Content Policy Framework + +## Purpose + +Create a comprehensive ai content policy framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai content policy framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: EU AI Act Transparency Obligations, China AI Labeling Requirements (2025), C2PA + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai content policy framework +- Identify gaps, opportunities, and risks +- Define success metrics: AI Content Labeling Compliance Rate, Deepfake Detection Accuracy, Content Policy Violation Rate, Copyright Claim Incidence +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai content policy framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Implement C2PA content credentials for all AI-generated media + +## Output Format + +```markdown +# AI Content Policy Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- EU AI Act Transparency Obligations +- China AI Labeling Requirements (2025) +- C2PA (Content Provenance and Authenticity) +- Platform-Specific Policies (Google/Meta/OpenAI) +- US Copyright Office Guidance + +## Key Metrics +- AI Content Labeling Compliance Rate +- Deepfake Detection Accuracy +- Content Policy Violation Rate (per 1000 generations) +- Copyright Claim Incidence +- User Trust Score +- Watermark Persistence Rate + +## Best Practices +- Implement C2PA content credentials for all AI-generated media +- Build content moderation as output guardrails, not afterthought filters (5 rail types) +- Maintain separate policies for text, image, audio, and video +- Track China labeling requirements — visible labels AND embedded metadata +- Document copyright provenance for all training data + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-cost-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-cost-optimization/SKILL.md new file mode 100644 index 0000000..2cb258a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-cost-optimization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai cost optimization with structured process, quality checks, and system integration +--- + +# AI Cost Optimization + +## Purpose + +Create a comprehensive ai cost optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai cost optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three-Tier Caching, Model Routing, Token Budget Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai cost optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Cost per Query (by model tier), Cache Hit Rate, Model Routing Distribution, Token Waste Ratio +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai cost optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Implement prompt caching first — 75% discount on cached tokens, highest ROI + +## Output Format + +```markdown +# AI Cost Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three-Tier Caching (Prompt/Exact/Semantic) +- Model Routing +- Token Budget Management +- Cost-per-Query Modeling +- Batch Processing APIs + +## Key Metrics +- Cost per Query (by model tier) +- Cache Hit Rate (prompt, exact, semantic) +- Model Routing Distribution +- Token Waste Ratio +- Cost-Quality Pareto Position +- Monthly API Spend Trend + +## Best Practices +- Implement prompt caching first — 75% discount on cached tokens, highest ROI +- Route by intent — simple queries to cheaper models, complex to capable (40-60% savings) +- Measure and optimize token consumption daily +- Use semantic caching cautiously — bad matching returns wrong cached results +- Model cost against quality on a Pareto curve for every use case + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-customer-service/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-customer-service/SKILL.md new file mode 100644 index 0000000..41aa00a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-customer-service/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai customer service with structured process, quality checks, and system integration +--- + +# Ai Customer Service + +## Purpose + +Create a comprehensive ai customer service that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai customer service documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai customer service +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai customer service using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Customer Service + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-data-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-data-analysis/SKILL.md new file mode 100644 index 0000000..0efa5b3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-data-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a ai data analysis with structured process, quality checks, and system integration +--- + +# Ai Data Analysis + +## Purpose + +Analyze and produce a comprehensive ai data analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai data analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai data analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai data analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Data Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-debugging-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-debugging-workflow/SKILL.md new file mode 100644 index 0000000..87b93e4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-debugging-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai debugging workflow with structured process, quality checks, and system integration +--- + +# Ai Debugging Workflow + +## Purpose + +Design and document a comprehensive ai debugging workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai debugging workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai debugging workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai debugging workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Debugging Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-editing-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-editing-workflow/SKILL.md new file mode 100644 index 0000000..7baf602 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-editing-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai editing workflow with structured process, quality checks, and system integration +--- + +# Ai Editing Workflow + +## Purpose + +Design and document a comprehensive ai editing workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai editing workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai editing workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai editing workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Editing Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-email-drafting/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-email-drafting/SKILL.md new file mode 100644 index 0000000..d83206a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-email-drafting/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai email drafting with structured process, quality checks, and system integration +--- + +# Ai Email Drafting + +## Purpose + +Create a comprehensive ai email drafting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai email drafting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai email drafting +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai email drafting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Email Drafting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-ethics-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-ethics-checklist/SKILL.md new file mode 100644 index 0000000..881ae7a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-ethics-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a ai ethics checklist with structured process, quality checks, and system integration +--- + +# Ai Ethics Checklist + +## Purpose + +Analyze and produce a comprehensive ai ethics checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai ethics checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai ethics checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai ethics checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Ethics Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-financial-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-financial-compliance/SKILL.md new file mode 100644 index 0000000..a2721af --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-financial-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai in financial services compliance with structured process, quality checks, and system integration +--- + +# AI in Financial Services Compliance + +## Purpose + +Create a comprehensive ai in financial services compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai in financial services compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SR 11-7, Fair Lending Laws (ECOA, FHA), BSA/AML + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai in financial services compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Model Inventory Completeness, Independent Validation Coverage, Fair Lending Disparity Metrics, Model Documentation Sufficiency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai in financial services compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Treat all AI/ML systems as models under SR 11-7 + +## Output Format + +```markdown +# AI in Financial Services Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SR 11-7 (Federal Reserve Model Risk Management) +- Fair Lending Laws (ECOA, FHA) +- BSA/AML +- OCC Comptroller Handbook +- SEC/FINRA AI Guidance + +## Key Metrics +- Model Inventory Completeness (SR 11-7) +- Independent Validation Coverage Rate +- Fair Lending Disparity Metrics +- Model Documentation Sufficiency Score +- Regulatory Examination Finding Rate +- Stress Test Coverage + +## Best Practices +- Treat all AI/ML systems as models under SR 11-7 broad definition +- Maintain documentation sufficient for unfamiliar parties +- Implement three validation pillars: conceptual soundness, ongoing monitoring, outcomes analysis +- Ensure effective challenge through independent, informed review +- Stress test under adverse scenarios — SR 11-7 warns about benign-condition optimism + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-healthcare-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-healthcare-compliance/SKILL.md new file mode 100644 index 0000000..59ffd04 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-healthcare-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai in healthcare compliance with structured process, quality checks, and system integration +--- + +# AI in Healthcare Compliance + +## Purpose + +Create a comprehensive ai in healthcare compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai in healthcare compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: FDA AI/ML Medical Device Framework, PCCP, GMLP (10 principles) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai in healthcare compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Regulatory Pathway Clearance Rate, PCCP Approval Coverage, Clinical Validation Evidence Strength, Adverse Event Reporting Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai in healthcare compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Determine SaMD classification early using IMDRF framework + +## Output Format + +```markdown +# AI in Healthcare Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- FDA AI/ML Medical Device Framework (510(k)/De Novo/PMA) +- Predetermined Change Control Plan (PCCP) +- Good Machine Learning Practice (GMLP) +- HIPAA +- EU MDR + AI Act intersection + +## Key Metrics +- Regulatory Pathway Clearance Rate +- PCCP Approval Coverage +- Clinical Validation Evidence Strength +- Adverse Event Reporting Compliance +- Real-World Performance Drift Detection Time +- SaMD Classification Accuracy + +## Best Practices +- Determine SaMD classification early using IMDRF framework +- Build PCCPs into initial submission for continuous learning systems +- Follow the 10 GMLP principles from day one +- Separate training data governance (HIPAA) from clinical validation (FDA evidence) +- Implement real-world performance monitoring with drift detection post-market + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-prompt/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-prompt/SKILL.md new file mode 100644 index 0000000..b5c70b5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-prompt/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai image prompt with structured process, quality checks, and system integration +--- + +# Ai Image Prompt + +## Purpose + +Create a comprehensive ai image prompt that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai image prompt documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai image prompt +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai image prompt using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Image Prompt + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-workflow/SKILL.md new file mode 100644 index 0000000..0caf794 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-image-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai image workflow with structured process, quality checks, and system integration +--- + +# Ai Image Workflow + +## Purpose + +Design and document a comprehensive ai image workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai image workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai image workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai image workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Image Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-meeting-notes/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-meeting-notes/SKILL.md new file mode 100644 index 0000000..5b4c59b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-meeting-notes/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai meeting notes with structured process, quality checks, and system integration +--- + +# Ai Meeting Notes + +## Purpose + +Create a comprehensive ai meeting notes that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai meeting notes documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai meeting notes +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai meeting notes using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Meeting Notes + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-pair-programming/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-pair-programming/SKILL.md new file mode 100644 index 0000000..83793da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-pair-programming/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai pair programming with structured process, quality checks, and system integration +--- + +# Ai Pair Programming + +## Purpose + +Design and document a comprehensive ai pair programming that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai pair programming documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai pair programming +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai pair programming using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Pair Programming + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-readiness-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-readiness-assessment/SKILL.md new file mode 100644 index 0000000..74ae662 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-readiness-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a ai readiness assessment with structured process, quality checks, and system integration +--- + +# Ai Readiness Assessment + +## Purpose + +Analyze and produce a comprehensive ai readiness assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai readiness assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai readiness assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai readiness assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Readiness Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-research-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-research-workflow/SKILL.md new file mode 100644 index 0000000..ff3611b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-research-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai research workflow with structured process, quality checks, and system integration +--- + +# Ai Research Workflow + +## Purpose + +Design and document a comprehensive ai research workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai research workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai research workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai research workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Research Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-strategy/SKILL.md new file mode 100644 index 0000000..029415d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai strategy with structured process, quality checks, and system integration +--- + +# Ai Strategy + +## Purpose + +Design and document a comprehensive ai strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-summarization/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-summarization/SKILL.md new file mode 100644 index 0000000..35c86b9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-summarization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai summarization with structured process, quality checks, and system integration +--- + +# Ai Summarization + +## Purpose + +Create a comprehensive ai summarization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai summarization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai summarization +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai summarization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Summarization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-training-program/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-training-program/SKILL.md new file mode 100644 index 0000000..fe86d1e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-training-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai training program with structured process, quality checks, and system integration +--- + +# Ai Training Program + +## Purpose + +Design and document a comprehensive ai training program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai training program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai training program +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai training program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Training Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-transcription-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-transcription-workflow/SKILL.md new file mode 100644 index 0000000..9f23872 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-transcription-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai transcription workflow with structured process, quality checks, and system integration +--- + +# Ai Transcription Workflow + +## Purpose + +Design and document a comprehensive ai transcription workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai transcription workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai transcription workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai transcription workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Transcription Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-translation-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-translation-workflow/SKILL.md new file mode 100644 index 0000000..9cdc44c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-translation-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai translation workflow with structured process, quality checks, and system integration +--- + +# Ai Translation Workflow + +## Purpose + +Design and document a comprehensive ai translation workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai translation workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai translation workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai translation workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Translation Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-use-case-identification/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-use-case-identification/SKILL.md new file mode 100644 index 0000000..9bfbec3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-use-case-identification/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai use case identification with structured process, quality checks, and system integration +--- + +# Ai Use Case Identification + +## Purpose + +Create a comprehensive ai use case identification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai use case identification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai use case identification +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai use case identification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Use Case Identification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-ux-design-patterns/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-ux-design-patterns/SKILL.md new file mode 100644 index 0000000..9b4f370 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-ux-design-patterns/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai ux design patterns with structured process, quality checks, and system integration +--- + +# AI UX Design Patterns + +## Purpose + +Create a comprehensive ai ux design patterns that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai ux design patterns documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Intent-Based Outcome Specification (NN/g), Hybrid Interface Pattern, Progressive Refinement + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai ux design patterns +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate with AI vs. Without, User Correction Rate, Time-to-First-Useful-Result, Trust Calibration Accuracy +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai ux design patterns using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Design hybrid interfaces, never pure chat — half the population has limited writing proficiency + +## Output Format + +```markdown +# AI UX Design Patterns + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Intent-Based Outcome Specification (NN/g Third UI Paradigm) +- Hybrid Interface Pattern (AI + traditional GUI) +- Progressive Refinement +- Transparency-Trust Framework +- Human-in-the-Loop Patterns + +## Key Metrics +- Task Completion Rate with AI vs. Without +- User Correction Rate +- Time-to-First-Useful-Result +- Trust Calibration Accuracy +- Fallback-to-Human Escalation Rate +- User Satisfaction Score + +## Best Practices +- Design hybrid interfaces, never pure chat — half the population has limited writing proficiency +- Stream output to reduce perceived latency (5s wait becomes engaging progressive reveal) +- Communicate uncertainty explicitly — show confidence levels, source attributions +- Design for iterative refinement, not one-shot perfection +- Implement graceful degradation with human fallback for out-of-scope queries + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-vendor-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-vendor-evaluation/SKILL.md new file mode 100644 index 0000000..0b75074 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-vendor-evaluation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ai vendor evaluation with structured process, quality checks, and system integration +--- + +# AI Vendor Evaluation + +## Purpose + +Create a comprehensive ai vendor evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai vendor evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SR 11-7 Vendor Model Requirements, NIST AI RMF Govern Function, SOC 2 + AI-Specific Controls + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai vendor evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Model Quality Benchmarks, Security Posture Score, Compliance Certificate Coverage, Total Cost of Ownership (3-year) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai vendor evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Apply SR 11-7 documentation standards to vendor AI, not just internal models + +## Output Format + +```markdown +# AI Vendor Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SR 11-7 Vendor Model Requirements +- NIST AI RMF Govern Function +- SOC 2 + AI-Specific Controls +- Model Card/System Card Framework +- Total Cost of Ownership (TCO) Model + +## Key Metrics +- Model Quality Benchmarks (domain-specific) +- Security Posture Score +- Compliance Certificate Coverage +- Total Cost of Ownership (3-year) +- Vendor Lock-In Score +- Model Card Completeness + +## Best Practices +- Apply SR 11-7 documentation standards to vendor AI, not just internal models +- Evaluate on YOUR data and use cases, not vendor benchmarks +- Assess lock-in across four dimensions: API, data, model format, integration depth +- Require model cards or system cards from every vendor +- Build a multi-vendor strategy with a model gateway for provider abstraction + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-voice-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-voice-workflow/SKILL.md new file mode 100644 index 0000000..fb2487a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-voice-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai voice workflow with structured process, quality checks, and system integration +--- + +# Ai Voice Workflow + +## Purpose + +Design and document a comprehensive ai voice workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai voice workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai voice workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai voice workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Voice Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-workflow-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-workflow-design/SKILL.md new file mode 100644 index 0000000..4cf3ac7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-workflow-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ai workflow design with structured process, quality checks, and system integration +--- + +# Ai Workflow Design + +## Purpose + +Create a comprehensive ai workflow design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai workflow design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai workflow design +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai workflow design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Workflow Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/ai-writing-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/ai-writing-workflow/SKILL.md new file mode 100644 index 0000000..ed1d0da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/ai-writing-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai writing workflow with structured process, quality checks, and system integration +--- + +# Ai Writing Workflow + +## Purpose + +Design and document a comprehensive ai writing workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai writing workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai writing workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai writing workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Ai Writing Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/algorithmic-impact-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/algorithmic-impact-assessment/SKILL.md new file mode 100644 index 0000000..5561e64 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/algorithmic-impact-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a algorithmic impact assessment with structured process, quality checks, and system integration +--- + +# Algorithmic Impact Assessment + +## Purpose + +Create a comprehensive algorithmic impact assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing algorithmic impact assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Canada AIA Tool, EU AI Act Fundamental Rights Impact Assessment, DPIA-AIA Integration + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the algorithmic impact assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Risk Score per System, Stakeholder Groups Consulted, Identified vs. Mitigated Risks Ratio, Fundamental Rights Impact Severity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the algorithmic impact assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Conduct impact assessments BEFORE deployment, not after incidents + +## Output Format + +```markdown +# Algorithmic Impact Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Canada Algorithmic Impact Assessment Tool +- EU AI Act Fundamental Rights Impact Assessment +- DPIA-AIA Integration (GDPR Article 35) +- AI Now Institute Framework +- IEEE 7010 + +## Key Metrics +- Risk Score per System (Canada AIA: 1-4) +- Stakeholder Groups Consulted +- Identified vs. Mitigated Risks Ratio +- Fundamental Rights Impact Severity +- Pre-Deployment Assessment Completion Rate +- Community Consultation Count + +## Best Practices +- Conduct impact assessments BEFORE deployment, not after incidents +- Include affected community stakeholders, not just internal reviewers +- Assess across five dimensions: purpose, data, model, deployment, impact +- Integrate AIA with existing DPIA processes for data-heavy AI +- Assign impact levels with proportionate controls (Level 1: docs only to Level 4: public consultation) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/api-integration-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/api-integration-plan/SKILL.md new file mode 100644 index 0000000..b34e6b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/api-integration-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a api integration plan with structured process, quality checks, and system integration +--- + +# Api Integration Plan + +## Purpose + +Design and document a comprehensive api integration plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api integration plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api integration plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api integration plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Api Integration Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/automation-opportunity-map/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/automation-opportunity-map/SKILL.md new file mode 100644 index 0000000..0e16330 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/automation-opportunity-map/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a automation opportunity map with structured process, quality checks, and system integration +--- + +# Automation Opportunity Map + +## Purpose + +Create a comprehensive automation opportunity map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing automation opportunity map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the automation opportunity map +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the automation opportunity map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Automation Opportunity Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/automation-roi-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/automation-roi-calculator/SKILL.md new file mode 100644 index 0000000..195c61a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/automation-roi-calculator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a automation roi calculator with structured process, quality checks, and system integration +--- + +# Automation Roi Calculator + +## Purpose + +Create a comprehensive automation roi calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing automation roi calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the automation roi calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the automation roi calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Automation Roi Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/chatbot-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/chatbot-design/SKILL.md new file mode 100644 index 0000000..d9a9bfd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/chatbot-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a chatbot design with structured process, quality checks, and system integration +--- + +# Chatbot Design + +## Purpose + +Create a comprehensive chatbot design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chatbot design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chatbot design +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chatbot design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Chatbot Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/conversational-flow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/conversational-flow/SKILL.md new file mode 100644 index 0000000..6dbf86e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/conversational-flow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a conversational flow with structured process, quality checks, and system integration +--- + +# Conversational Flow + +## Purpose + +Create a comprehensive conversational flow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conversational flow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conversational flow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conversational flow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Conversational Flow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/creative-ai-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/creative-ai-brief/SKILL.md new file mode 100644 index 0000000..d671c68 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/creative-ai-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a creative ai brief with structured process, quality checks, and system integration +--- + +# Creative Ai Brief + +## Purpose + +Create a comprehensive creative ai brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing creative ai brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the creative ai brief +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the creative ai brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Creative Ai Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/enterprise-ai-governance/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/enterprise-ai-governance/SKILL.md new file mode 100644 index 0000000..8bd8a98 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/enterprise-ai-governance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a enterprise ai governance with structured process, quality checks, and system integration +--- + +# Enterprise AI Governance + +## Purpose + +Create a comprehensive enterprise ai governance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing enterprise ai governance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO 42001, NIST AI RMF 1.0, SR 11-7 (Federal Reserve) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the enterprise ai governance +- Identify gaps, opportunities, and risks +- Define success metrics: Model Inventory Completeness, Risk Tier Distribution, Mean Time to Approval, Independent Validation Coverage +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the enterprise ai governance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Maintain a comprehensive model inventory — you cannot govern what you cannot see + +## Output Format + +```markdown +# Enterprise AI Governance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO 42001 (AI Management System) +- NIST AI RMF 1.0 (Govern/Map/Measure/Manage) +- SR 11-7 (Federal Reserve Model Risk Management) +- IEEE 7000 +- OECD AI Principles + +## Key Metrics +- Model Inventory Completeness (% registered) +- Risk Tier Distribution +- Mean Time from Submission to Approval +- Independent Validation Coverage Rate +- Post-Deployment Alert Resolution Time +- Governance Board Meeting Frequency + +## Best Practices +- Maintain a comprehensive model inventory — you cannot govern what you cannot see +- Implement risk-tiered governance with proportionate controls +- Require effective challenge through independent review (SR 11-7) +- Document sufficiently for unfamiliar parties +- Conduct validation especially during benign conditions — AI optimism is most dangerous when things look fine + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/eu-ai-act-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/eu-ai-act-compliance/SKILL.md new file mode 100644 index 0000000..08f1601 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/eu-ai-act-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a eu ai act compliance with structured process, quality checks, and system integration +--- + +# EU AI Act Compliance + +## Purpose + +Create a comprehensive eu ai act compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing eu ai act compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: EU AI Act (Regulation 2024/1689), ISO 42001, CEN/CENELEC AI Standards + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the eu ai act compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Risk Classification Accuracy, Technical Documentation Completeness, Conformity Assessment Pass Rate, Time-to-Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the eu ai act compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Classify every AI system against the four risk tiers early — unacceptable risk systems are banned since Feb 2025 + +## Output Format + +```markdown +# EU AI Act Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- EU AI Act (Regulation 2024/1689) +- ISO 42001 +- CEN/CENELEC AI Standards +- NIST AI RMF +- OECD AI Principles + +## Key Metrics +- Risk Classification Accuracy per AI System +- Technical Documentation Completeness (Annex IV) +- Conformity Assessment Pass Rate +- Time-to-Compliance per AI System +- Post-Market Monitoring Incident Response Time +- GPAI Obligation Coverage + +## Best Practices +- Classify every AI system against the four risk tiers early — unacceptable risk systems are banned since Feb 2025 +- Build Annex IV technical documentation as a living artifact +- Implement quality management systems before August 2026 full applicability +- Prepare GPAI obligations by August 2025 +- Establish post-market surveillance workflows for deployed systems + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/fine-tuning-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/fine-tuning-plan/SKILL.md new file mode 100644 index 0000000..4f0f256 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/fine-tuning-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a fine tuning plan with structured process, quality checks, and system integration +--- + +# Fine Tuning Plan + +## Purpose + +Design and document a comprehensive fine tuning plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fine tuning plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fine tuning plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fine tuning plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Fine Tuning Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/intelligent-automation/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/intelligent-automation/SKILL.md new file mode 100644 index 0000000..4f947da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/intelligent-automation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a intelligent automation with structured process, quality checks, and system integration +--- + +# Intelligent Automation + +## Purpose + +Create a comprehensive intelligent automation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing intelligent automation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the intelligent automation +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the intelligent automation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Intelligent Automation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/knowledge-base-ai/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/knowledge-base-ai/SKILL.md new file mode 100644 index 0000000..2e3f7cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/knowledge-base-ai/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a knowledge base ai with structured process, quality checks, and system integration +--- + +# Knowledge Base Ai + +## Purpose + +Create a comprehensive knowledge base ai that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing knowledge base ai documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the knowledge base ai +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the knowledge base ai using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Knowledge Base Ai + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/llm-application-architecture/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/llm-application-architecture/SKILL.md new file mode 100644 index 0000000..9b1a632 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/llm-application-architecture/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a llm application architecture with structured process, quality checks, and system integration +--- + +# LLM Application Architecture + +## Purpose + +Create a comprehensive llm application architecture that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing llm application architecture documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Anthropic 6 Agent Patterns, RAG Architecture, GenAI Platform Stack + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the llm application architecture +- Identify gaps, opportunities, and risks +- Define success metrics: TTFT (Time to First Token), Retrieval Precision/Recall, Guardrail Trigger Rate, End-to-End Latency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the llm application architecture using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start simple — many applications need only optimized single LLM calls with retrieval + +## Output Format + +```markdown +# LLM Application Architecture + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Anthropic 6 Agent Patterns (Chaining, Routing, Parallelization, Orchestrator-Workers, Evaluator-Optimizer, Autonomous) +- RAG Architecture (Term+Embedding+Hybrid+Reranking) +- GenAI Platform Stack +- LangChain/LangGraph +- Model Gateway Pattern + +## Key Metrics +- TTFT (Time to First Token) +- Retrieval Precision/Recall +- Guardrail Trigger Rate (FP and TP) +- End-to-End Latency per Pattern +- Cost per Query across Routing Tiers +- Agent Task Completion Rate + +## Best Practices +- Start simple — many applications need only optimized single LLM calls with retrieval +- Use routing to match query complexity to model cost (40-60% savings) +- Implement guardrails as a parallel layer, not serial bottleneck +- Build RAG with cheap retriever then expensive reranker sequential pattern +- Invest in tool/API interface design — poor tool descriptions are the primary cause of agent failures + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/llm-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/llm-comparison/SKILL.md new file mode 100644 index 0000000..8684b26 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/llm-comparison/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a llm comparison with structured process, quality checks, and system integration +--- + +# Llm Comparison + +## Purpose + +Analyze and produce a comprehensive llm comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing llm comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the llm comparison +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the llm comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Llm Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/make-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/make-workflow/SKILL.md new file mode 100644 index 0000000..6fb5523 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/make-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a make workflow with structured process, quality checks, and system integration +--- + +# Make Workflow + +## Purpose + +Design and document a comprehensive make workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing make workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the make workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the make workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Make Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/multi-agent-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/multi-agent-workflow/SKILL.md new file mode 100644 index 0000000..baee765 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/multi-agent-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a multi agent workflow with structured process, quality checks, and system integration +--- + +# Multi Agent Workflow + +## Purpose + +Design and document a comprehensive multi agent workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing multi agent workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the multi agent workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the multi agent workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Multi Agent Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/n8n-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/n8n-workflow/SKILL.md new file mode 100644 index 0000000..08cbe78 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/n8n-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a n8n workflow with structured process, quality checks, and system integration +--- + +# N8n Workflow + +## Purpose + +Design and document a comprehensive n8n workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing n8n workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the n8n workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the n8n workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# N8n Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/no-code-automation/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/no-code-automation/SKILL.md new file mode 100644 index 0000000..8f1f7fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/no-code-automation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a no code automation with structured process, quality checks, and system integration +--- + +# No Code Automation + +## Purpose + +Create a comprehensive no code automation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing no code automation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the no code automation +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the no code automation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# No Code Automation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/process-mining/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/process-mining/SKILL.md new file mode 100644 index 0000000..476b8e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/process-mining/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a process mining with structured process, quality checks, and system integration +--- + +# Process Mining + +## Purpose + +Create a comprehensive process mining that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing process mining documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the process mining +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the process mining using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Process Mining + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/prompt-engineering-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-engineering-guide/SKILL.md new file mode 100644 index 0000000..c725c64 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-engineering-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a prompt engineering guide with structured process, quality checks, and system integration +--- + +# Prompt Engineering Guide + +## Purpose + +Design and document a comprehensive prompt engineering guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prompt engineering guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prompt engineering guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prompt engineering guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Prompt Engineering Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/prompt-evaluation-harness/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-evaluation-harness/SKILL.md new file mode 100644 index 0000000..5e8f713 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-evaluation-harness/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a prompt evaluation harness with structured process, quality checks, and system integration +--- + +# Prompt Evaluation Harness + +## Purpose + +Create a comprehensive prompt evaluation harness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prompt evaluation harness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: DeepEval (50+ metrics), RAGAS, HELM (Stanford) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prompt evaluation harness +- Identify gaps, opportunities, and risks +- Define success metrics: Faithfulness Score, Answer Relevancy, Hallucination Rate, Contextual Precision/Recall +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prompt evaluation harness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Treat prompt evaluation like unit testing — use pytest-style test suites in CI/CD + +## Output Format + +```markdown +# Prompt Evaluation Harness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- DeepEval (50+ metrics) +- RAGAS (RAG-specific evaluation) +- HELM (Stanford curated benchmarks) +- BIG-bench +- Custom Evals (model-generated, human-verified) + +## Key Metrics +- Faithfulness Score +- Answer Relevancy +- Hallucination Rate +- Contextual Precision/Recall +- Regression Rate Across Prompt Versions +- Human-AI Agreement Score + +## Best Practices +- Treat prompt evaluation like unit testing — use pytest-style test suites in CI/CD +- Evaluate at both component and end-to-end levels using LLM tracing +- Use LLM-as-judge with research-backed metrics (G-Eval), not vibes +- Run regression testing across prompt versions +- Combine automated and human evaluation — human for high-stakes, automated for continuous + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/prompt-template-builder/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-template-builder/SKILL.md new file mode 100644 index 0000000..1375e6a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-template-builder/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a prompt template builder with structured process, quality checks, and system integration +--- + +# Prompt Template Builder + +## Purpose + +Create a comprehensive prompt template builder that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prompt template builder documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prompt template builder +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prompt template builder using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Prompt Template Builder + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/prompt-testing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-testing-plan/SKILL.md new file mode 100644 index 0000000..2d8015a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/prompt-testing-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a prompt testing plan with structured process, quality checks, and system integration +--- + +# Prompt Testing Plan + +## Purpose + +Design and document a comprehensive prompt testing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prompt testing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prompt testing plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prompt testing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Prompt Testing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/rag-system-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/rag-system-design/SKILL.md new file mode 100644 index 0000000..75a9af1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/rag-system-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a rag system design with structured process, quality checks, and system integration +--- + +# Rag System Design + +## Purpose + +Create a comprehensive rag system design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rag system design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rag system design +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rag system design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Rag System Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/responsible-ai-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/responsible-ai-framework/SKILL.md new file mode 100644 index 0000000..34db5b1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/responsible-ai-framework/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a responsible ai framework with structured process, quality checks, and system integration +--- + +# Responsible Ai Framework + +## Purpose + +Design and document a comprehensive responsible ai framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing responsible ai framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the responsible ai framework +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the responsible ai framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Responsible Ai Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/rpa-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/rpa-assessment/SKILL.md new file mode 100644 index 0000000..c66f6fc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/rpa-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a rpa assessment with structured process, quality checks, and system integration +--- + +# Rpa Assessment + +## Purpose + +Analyze and produce a comprehensive rpa assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rpa assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rpa assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rpa assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Rpa Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/synthetic-data-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/synthetic-data-strategy/SKILL.md new file mode 100644 index 0000000..17ba0cd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/synthetic-data-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a synthetic data strategy with structured process, quality checks, and system integration +--- + +# Synthetic Data Strategy + +## Purpose + +Create a comprehensive synthetic data strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing synthetic data strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GAN-Based Generation, LLM-Based Generation (Self-Instruct), Statistical Model Fitting + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the synthetic data strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Fidelity Score, Utility Score, Privacy Score (Re-identification Risk), Diversity Coverage +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the synthetic data strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Validate against all three dimensions: fidelity, utility, and privacy + +## Output Format + +```markdown +# Synthetic Data Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GAN-Based Generation +- LLM-Based Generation (Self-Instruct) +- Statistical Model Fitting +- Differential Privacy Integration +- Transfer Learning Pipeline + +## Key Metrics +- Fidelity Score (statistical similarity to real data) +- Utility Score (downstream model performance) +- Privacy Score (re-identification risk) +- Diversity Coverage (edge case representation) +- Generation Cost vs. Real Data Cost Ratio +- Membership Inference Attack Resistance + +## Best Practices +- Validate against all three dimensions: fidelity, utility, and privacy +- Use synthetic data to augment, not replace, real data +- Apply Self-Instruct techniques for NLP/LLM training data +- Test for membership inference attacks before releasing synthetic datasets +- Use synthetic data for testing fraud detection and security systems + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/webhook-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/webhook-design/SKILL.md new file mode 100644 index 0000000..34856dd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/webhook-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a webhook design with structured process, quality checks, and system integration +--- + +# Webhook Design + +## Purpose + +Create a comprehensive webhook design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing webhook design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the webhook design +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the webhook design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Webhook Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ai-automation/zapier-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/ai-automation/zapier-workflow/SKILL.md new file mode 100644 index 0000000..a895895 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ai-automation/zapier-workflow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a zapier workflow with structured process, quality checks, and system integration +--- + +# Zapier Workflow + +## Purpose + +Design and document a comprehensive zapier workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: AI & Automation + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing zapier workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AI Readiness Assessment, Automation ROI Calculator, Human-in-the-Loop Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the zapier workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Time Saved Per Task, Automation Rate, Error Reduction %, Cost Per AI Operation +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the zapier workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with high-volume, low-risk tasks + +## Output Format + +```markdown +# Zapier Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AI Readiness Assessment +- Automation ROI Calculator +- Human-in-the-Loop Design +- RAG Architecture +- Agent Orchestration Patterns +- Responsible AI Framework + +## Key Metrics +- Time Saved Per Task +- Automation Rate +- Error Reduction % +- Cost Per AI Operation +- User Adoption Rate +- Output Quality Score + +## Best Practices +- Start with high-volume, low-risk tasks +- Always keep human review for critical outputs +- Measure time saved, not just accuracy +- Version control prompts like code +- Monitor for drift and degradation monthly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/apprenticeship-program/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/apprenticeship-program/SKILL.md new file mode 100644 index 0000000..372408e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/apprenticeship-program/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a apprenticeship program with structured process, quality checks, and system integration +--- + +# Apprenticeship Program + +## Purpose + +Design and document a comprehensive apprenticeship program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing apprenticeship program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the apprenticeship program +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the apprenticeship program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Apprenticeship Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/as-built-documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/as-built-documentation/SKILL.md new file mode 100644 index 0000000..83c3a0b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/as-built-documentation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a as built documentation with structured process, quality checks, and system integration +--- + +# As Built Documentation + +## Purpose + +Create a comprehensive as built documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing as built documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the as built documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the as built documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# As Built Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/bid-submission/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/bid-submission/SKILL.md new file mode 100644 index 0000000..73c51c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/bid-submission/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a bid submission with structured process, quality checks, and system integration +--- + +# Bid Submission + +## Purpose + +Create a comprehensive bid submission that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bid submission documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bid submission +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bid submission using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Bid Submission + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/budget-tracking-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/budget-tracking-construction/SKILL.md new file mode 100644 index 0000000..5e082d5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/budget-tracking-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a budget tracking construction with structured process, quality checks, and system integration +--- + +# Budget Tracking Construction + +## Purpose + +Create a comprehensive budget tracking construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing budget tracking construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the budget tracking construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the budget tracking construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Budget Tracking Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/change-order/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/change-order/SKILL.md new file mode 100644 index 0000000..d469938 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/change-order/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a change order with structured process, quality checks, and system integration +--- + +# Change Order + +## Purpose + +Create a comprehensive change order that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing change order documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the change order +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the change order using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Change Order + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/client-update-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/client-update-construction/SKILL.md new file mode 100644 index 0000000..35f2bef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/client-update-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a client update construction with structured process, quality checks, and system integration +--- + +# Client Update Construction + +## Purpose + +Create a comprehensive client update construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client update construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client update construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client update construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Client Update Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/code-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/code-compliance/SKILL.md new file mode 100644 index 0000000..40f6b26 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/code-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a code compliance with structured process, quality checks, and system integration +--- + +# Code Compliance + +## Purpose + +Create a comprehensive code compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing code compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the code compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the code compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Code Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/completion-certificate/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/completion-certificate/SKILL.md new file mode 100644 index 0000000..d3e1af0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/completion-certificate/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a completion certificate with structured process, quality checks, and system integration +--- + +# Completion Certificate + +## Purpose + +Create a comprehensive completion certificate that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing completion certificate documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the completion certificate +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the completion certificate using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Completion Certificate + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/cost-variance-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/cost-variance-analysis/SKILL.md new file mode 100644 index 0000000..34250ca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/cost-variance-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a cost variance analysis with structured process, quality checks, and system integration +--- + +# Cost Variance Analysis + +## Purpose + +Analyze and produce a comprehensive cost variance analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost variance analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost variance analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost variance analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Cost Variance Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/critical-path/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/critical-path/SKILL.md new file mode 100644 index 0000000..1ff2953 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/critical-path/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a critical path with structured process, quality checks, and system integration +--- + +# Critical Path + +## Purpose + +Create a comprehensive critical path that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing critical path documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the critical path +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the critical path using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Critical Path + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/employee-certification-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/employee-certification-tracker/SKILL.md new file mode 100644 index 0000000..b5eeefd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/employee-certification-tracker/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a employee certification tracker with structured process, quality checks, and system integration +--- + +# Employee Certification Tracker + +## Purpose + +Analyze and produce a comprehensive employee certification tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employee certification tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employee certification tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employee certification tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Employee Certification Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/environmental-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/environmental-assessment/SKILL.md new file mode 100644 index 0000000..1f07378 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/environmental-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a environmental assessment with structured process, quality checks, and system integration +--- + +# Environmental Assessment + +## Purpose + +Analyze and produce a comprehensive environmental assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing environmental assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the environmental assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the environmental assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Environmental Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/equipment-maintenance/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/equipment-maintenance/SKILL.md new file mode 100644 index 0000000..f7c70b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/equipment-maintenance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a equipment maintenance with structured process, quality checks, and system integration +--- + +# Equipment Maintenance + +## Purpose + +Create a comprehensive equipment maintenance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing equipment maintenance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the equipment maintenance +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the equipment maintenance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Equipment Maintenance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/fleet-management/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/fleet-management/SKILL.md new file mode 100644 index 0000000..40dfa36 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/fleet-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a fleet management with structured process, quality checks, and system integration +--- + +# Fleet Management + +## Purpose + +Create a comprehensive fleet management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fleet management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fleet management +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fleet management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Fleet Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/gantt-chart-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/gantt-chart-construction/SKILL.md new file mode 100644 index 0000000..20cabe6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/gantt-chart-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a gantt chart construction with structured process, quality checks, and system integration +--- + +# Gantt Chart Construction + +## Purpose + +Create a comprehensive gantt chart construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gantt chart construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gantt chart construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gantt chart construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Gantt Chart Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/incident-report/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/incident-report/SKILL.md new file mode 100644 index 0000000..6bae643 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/incident-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a incident report with structured process, quality checks, and system integration +--- + +# Incident Report + +## Purpose + +Analyze and produce a comprehensive incident report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident report +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Incident Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/inspection-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/inspection-checklist/SKILL.md new file mode 100644 index 0000000..1d08506 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/inspection-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a inspection checklist with structured process, quality checks, and system integration +--- + +# Inspection Checklist + +## Purpose + +Analyze and produce a comprehensive inspection checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inspection checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inspection checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inspection checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Inspection Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/labor-estimate/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/labor-estimate/SKILL.md new file mode 100644 index 0000000..39dfcb2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/labor-estimate/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a labor estimate with structured process, quality checks, and system integration +--- + +# Labor Estimate + +## Purpose + +Create a comprehensive labor estimate that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing labor estimate documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the labor estimate +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the labor estimate using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Labor Estimate + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/maintenance-manual/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/maintenance-manual/SKILL.md new file mode 100644 index 0000000..23e07aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/maintenance-manual/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a maintenance manual with structured process, quality checks, and system integration +--- + +# Maintenance Manual + +## Purpose + +Create a comprehensive maintenance manual that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing maintenance manual documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the maintenance manual +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the maintenance manual using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Maintenance Manual + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/marketing-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/marketing-construction/SKILL.md new file mode 100644 index 0000000..3e9e140 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/marketing-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a marketing construction with structured process, quality checks, and system integration +--- + +# Marketing Construction + +## Purpose + +Create a comprehensive marketing construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Marketing Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/material-takeoff/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/material-takeoff/SKILL.md new file mode 100644 index 0000000..cdbdbce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/material-takeoff/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a material takeoff with structured process, quality checks, and system integration +--- + +# Material Takeoff + +## Purpose + +Create a comprehensive material takeoff that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing material takeoff documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the material takeoff +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the material takeoff using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Material Takeoff + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/payment-application/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/payment-application/SKILL.md new file mode 100644 index 0000000..93857ab --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/payment-application/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a payment application with structured process, quality checks, and system integration +--- + +# Payment Application + +## Purpose + +Create a comprehensive payment application that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing payment application documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the payment application +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the payment application using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Payment Application + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/permit-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/permit-checklist/SKILL.md new file mode 100644 index 0000000..af35ac8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/permit-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a permit checklist with structured process, quality checks, and system integration +--- + +# Permit Checklist + +## Purpose + +Analyze and produce a comprehensive permit checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing permit checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the permit checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the permit checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Permit Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/portfolio-showcase/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/portfolio-showcase/SKILL.md new file mode 100644 index 0000000..5563edb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/portfolio-showcase/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a portfolio showcase with structured process, quality checks, and system integration +--- + +# Portfolio Showcase + +## Purpose + +Create a comprehensive portfolio showcase that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing portfolio showcase documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the portfolio showcase +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the portfolio showcase using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Portfolio Showcase + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/progress-report-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/progress-report-construction/SKILL.md new file mode 100644 index 0000000..b07dd5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/progress-report-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a progress report construction with structured process, quality checks, and system integration +--- + +# Progress Report Construction + +## Purpose + +Analyze and produce a comprehensive progress report construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing progress report construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the progress report construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the progress report construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Progress Report Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/project-estimate/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/project-estimate/SKILL.md new file mode 100644 index 0000000..11aff8a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/project-estimate/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a project estimate with structured process, quality checks, and system integration +--- + +# Project Estimate + +## Purpose + +Create a comprehensive project estimate that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project estimate documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project estimate +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project estimate using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Project Estimate + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/project-proposal-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/project-proposal-construction/SKILL.md new file mode 100644 index 0000000..13353cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/project-proposal-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a project proposal construction with structured process, quality checks, and system integration +--- + +# Project Proposal Construction + +## Purpose + +Create a comprehensive project proposal construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project proposal construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project proposal construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project proposal construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Project Proposal Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/project-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/project-schedule/SKILL.md new file mode 100644 index 0000000..ed2b552 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/project-schedule/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a project schedule with structured process, quality checks, and system integration +--- + +# Project Schedule + +## Purpose + +Design and document a comprehensive project schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Project Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/punch-list/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/punch-list/SKILL.md new file mode 100644 index 0000000..f8224be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/punch-list/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a punch list with structured process, quality checks, and system integration +--- + +# Punch List + +## Purpose + +Create a comprehensive punch list that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing punch list documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the punch list +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the punch list using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Punch List + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/quality-control-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/quality-control-construction/SKILL.md new file mode 100644 index 0000000..ad13b4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/quality-control-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a quality control construction with structured process, quality checks, and system integration +--- + +# Quality Control Construction + +## Purpose + +Create a comprehensive quality control construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quality control construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quality control construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quality control construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Quality Control Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/referral-strategy-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/referral-strategy-construction/SKILL.md new file mode 100644 index 0000000..6eda1a2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/referral-strategy-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a referral strategy construction with structured process, quality checks, and system integration +--- + +# Referral Strategy Construction + +## Purpose + +Design and document a comprehensive referral strategy construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral strategy construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral strategy construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral strategy construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Referral Strategy Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/safety-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/safety-plan/SKILL.md new file mode 100644 index 0000000..afaf028 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/safety-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a safety plan with structured process, quality checks, and system integration +--- + +# Safety Plan + +## Purpose + +Design and document a comprehensive safety plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing safety plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the safety plan +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the safety plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Safety Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/safety-training/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/safety-training/SKILL.md new file mode 100644 index 0000000..c56118e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/safety-training/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a safety training with structured process, quality checks, and system integration +--- + +# Safety Training + +## Purpose + +Create a comprehensive safety training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing safety training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the safety training +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the safety training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Safety Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/scope-of-work-construction/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/scope-of-work-construction/SKILL.md new file mode 100644 index 0000000..59a7940 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/scope-of-work-construction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a scope of work construction with structured process, quality checks, and system integration +--- + +# Scope Of Work Construction + +## Purpose + +Create a comprehensive scope of work construction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scope of work construction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scope of work construction +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scope of work construction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Scope Of Work Construction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/site-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/site-assessment/SKILL.md new file mode 100644 index 0000000..b11d72c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/site-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a site assessment with structured process, quality checks, and system integration +--- + +# Site Assessment + +## Purpose + +Analyze and produce a comprehensive site assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing site assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the site assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the site assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Site Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/soil-report-summary/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/soil-report-summary/SKILL.md new file mode 100644 index 0000000..4950831 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/soil-report-summary/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a soil report summary with structured process, quality checks, and system integration +--- + +# Soil Report Summary + +## Purpose + +Analyze and produce a comprehensive soil report summary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soil report summary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soil report summary +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soil report summary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Soil Report Summary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/subcontractor-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/subcontractor-agreement/SKILL.md new file mode 100644 index 0000000..6d5abdd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/subcontractor-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a subcontractor agreement with structured process, quality checks, and system integration +--- + +# Subcontractor Agreement + +## Purpose + +Create a comprehensive subcontractor agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subcontractor agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subcontractor agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subcontractor agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Subcontractor Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/subcontractor-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/subcontractor-evaluation/SKILL.md new file mode 100644 index 0000000..7e1fa02 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/subcontractor-evaluation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a subcontractor evaluation with structured process, quality checks, and system integration +--- + +# Subcontractor Evaluation + +## Purpose + +Analyze and produce a comprehensive subcontractor evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subcontractor evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subcontractor evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subcontractor evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Subcontractor Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/tool-inventory/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/tool-inventory/SKILL.md new file mode 100644 index 0000000..3ad05c9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/tool-inventory/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a tool inventory with structured process, quality checks, and system integration +--- + +# Tool Inventory + +## Purpose + +Create a comprehensive tool inventory that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tool inventory documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tool inventory +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tool inventory using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Tool Inventory + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/toolbox-talk/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/toolbox-talk/SKILL.md new file mode 100644 index 0000000..eb15163 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/toolbox-talk/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a toolbox talk with structured process, quality checks, and system integration +--- + +# Toolbox Talk + +## Purpose + +Create a comprehensive toolbox talk that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing toolbox talk documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the toolbox talk +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the toolbox talk using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Toolbox Talk + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/warranty-document/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/warranty-document/SKILL.md new file mode 100644 index 0000000..31c9e75 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/warranty-document/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a warranty document with structured process, quality checks, and system integration +--- + +# Warranty Document + +## Purpose + +Create a comprehensive warranty document that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing warranty document documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the warranty document +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the warranty document using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Warranty Document + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/construction/zoning-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/construction/zoning-analysis/SKILL.md new file mode 100644 index 0000000..04a636e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/construction/zoning-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a zoning analysis with structured process, quality checks, and system integration +--- + +# Zoning Analysis + +## Purpose + +Analyze and produce a comprehensive zoning analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Construction & Trades + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing zoning analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Critical Path Method, Work Breakdown Structure, Earned Value Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the zoning analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Schedule Variance, Cost Variance, Safety Incident Rate, Rework Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the zoning analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Detailed scope before pricing + +## Output Format + +```markdown +# Zoning Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Critical Path Method +- Work Breakdown Structure +- Earned Value Management +- BIM (Building Information Modeling) +- Lean Construction + +## Key Metrics +- Schedule Variance +- Cost Variance +- Safety Incident Rate +- Rework Rate +- Change Order Frequency +- Client Satisfaction Score + +## Best Practices +- Detailed scope before pricing +- Daily safety briefings +- 10% contingency on all estimates +- Document changes in writing immediately +- Progress photos daily for accountability + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/100-day-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/100-day-plan/SKILL.md new file mode 100644 index 0000000..f5f180c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/100-day-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a 100 day plan with structured process, quality checks, and system integration +--- + +# 100 Day Plan + +## Purpose + +Design and document a comprehensive 100 day plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing 100 day plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the 100 day plan +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the 100 day plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# 100 Day Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/benchmarking-study/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/benchmarking-study/SKILL.md new file mode 100644 index 0000000..4dc4d09 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/benchmarking-study/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a benchmarking study with structured process, quality checks, and system integration +--- + +# Benchmarking Study + +## Purpose + +Analyze and produce a comprehensive benchmarking study that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing benchmarking study documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the benchmarking study +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the benchmarking study using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Benchmarking Study + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/board-presentation/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/board-presentation/SKILL.md new file mode 100644 index 0000000..be9fb62 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/board-presentation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a board presentation with structured process, quality checks, and system integration +--- + +# Board Presentation + +## Purpose + +Create a comprehensive board presentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board presentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board presentation +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board presentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Board Presentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/build-vs-buy/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/build-vs-buy/SKILL.md new file mode 100644 index 0000000..9f24cb4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/build-vs-buy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a build vs buy with structured process, quality checks, and system integration +--- + +# Build Vs Buy + +## Purpose + +Create a comprehensive build vs buy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing build vs buy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the build vs buy +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the build vs buy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Build Vs Buy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/capability-building/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/capability-building/SKILL.md new file mode 100644 index 0000000..944998e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/capability-building/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a capability building with structured process, quality checks, and system integration +--- + +# Capability Building + +## Purpose + +Create a comprehensive capability building that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing capability building documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the capability building +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the capability building using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Capability Building + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/change-readiness/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/change-readiness/SKILL.md new file mode 100644 index 0000000..15f8923 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/change-readiness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a change readiness with structured process, quality checks, and system integration +--- + +# Change Readiness + +## Purpose + +Create a comprehensive change readiness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing change readiness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the change readiness +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the change readiness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Change Readiness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/client-discovery-workshop/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/client-discovery-workshop/SKILL.md new file mode 100644 index 0000000..14d1449 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/client-discovery-workshop/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a client discovery workshop with structured process, quality checks, and system integration +--- + +# Client Discovery Workshop + +## Purpose + +Create a comprehensive client discovery workshop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client discovery workshop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client discovery workshop +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client discovery workshop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Client Discovery Workshop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/client-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/client-proposal/SKILL.md new file mode 100644 index 0000000..b3f63ec --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/client-proposal/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a client proposal with structured process, quality checks, and system integration +--- + +# Client Proposal + +## Purpose + +Create a comprehensive client proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Client Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/core-competency-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/core-competency-analysis/SKILL.md new file mode 100644 index 0000000..c0bba00 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/core-competency-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a core competency analysis with structured process, quality checks, and system integration +--- + +# Core Competency Analysis + +## Purpose + +Analyze and produce a comprehensive core competency analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing core competency analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the core competency analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the core competency analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Core Competency Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/cost-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/cost-optimization/SKILL.md new file mode 100644 index 0000000..df35a59 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/cost-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cost optimization with structured process, quality checks, and system integration +--- + +# Cost Optimization + +## Purpose + +Create a comprehensive cost optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Cost Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/culture-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/culture-assessment/SKILL.md new file mode 100644 index 0000000..6bb2a0f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/culture-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a culture assessment with structured process, quality checks, and system integration +--- + +# Culture Assessment + +## Purpose + +Analyze and produce a comprehensive culture assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing culture assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the culture assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the culture assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Culture Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/current-state-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/current-state-assessment/SKILL.md new file mode 100644 index 0000000..54871af --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/current-state-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a current state assessment with structured process, quality checks, and system integration +--- + +# Current State Assessment + +## Purpose + +Analyze and produce a comprehensive current state assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing current state assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the current state assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the current state assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Current State Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/customer-experience-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/customer-experience-audit/SKILL.md new file mode 100644 index 0000000..646abca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/customer-experience-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a customer experience audit with structured process, quality checks, and system integration +--- + +# Customer Experience Audit + +## Purpose + +Analyze and produce a comprehensive customer experience audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer experience audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer experience audit +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer experience audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Customer Experience Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/digital-transformation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/digital-transformation-plan/SKILL.md new file mode 100644 index 0000000..3e39560 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/digital-transformation-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a digital transformation plan with structured process, quality checks, and system integration +--- + +# Digital Transformation Plan + +## Purpose + +Design and document a comprehensive digital transformation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing digital transformation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the digital transformation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the digital transformation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Digital Transformation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/disruption-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/disruption-analysis/SKILL.md new file mode 100644 index 0000000..7adbc35 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/disruption-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a disruption analysis with structured process, quality checks, and system integration +--- + +# Disruption Analysis + +## Purpose + +Analyze and produce a comprehensive disruption analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing disruption analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the disruption analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the disruption analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Disruption Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/diversification-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/diversification-analysis/SKILL.md new file mode 100644 index 0000000..9b86cbe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/diversification-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a diversification analysis with structured process, quality checks, and system integration +--- + +# Diversification Analysis + +## Purpose + +Analyze and produce a comprehensive diversification analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing diversification analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the diversification analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the diversification analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Diversification Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/due-diligence-commercial/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/due-diligence-commercial/SKILL.md new file mode 100644 index 0000000..f5a8722 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/due-diligence-commercial/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a due diligence commercial with structured process, quality checks, and system integration +--- + +# Due Diligence Commercial + +## Purpose + +Create a comprehensive due diligence commercial that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing due diligence commercial documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the due diligence commercial +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the due diligence commercial using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Due Diligence Commercial + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/engagement-letter/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/engagement-letter/SKILL.md new file mode 100644 index 0000000..be9cc7f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/engagement-letter/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a engagement letter with structured process, quality checks, and system integration +--- + +# Engagement Letter + +## Purpose + +Create a comprehensive engagement letter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing engagement letter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the engagement letter +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the engagement letter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Engagement Letter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/executive-presentation/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/executive-presentation/SKILL.md new file mode 100644 index 0000000..5b614be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/executive-presentation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a executive presentation with structured process, quality checks, and system integration +--- + +# Executive Presentation + +## Purpose + +Create a comprehensive executive presentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive presentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive presentation +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive presentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Executive Presentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/expansion-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/expansion-strategy/SKILL.md new file mode 100644 index 0000000..498efdb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/expansion-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a expansion strategy with structured process, quality checks, and system integration +--- + +# Expansion Strategy + +## Purpose + +Design and document a comprehensive expansion strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing expansion strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the expansion strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the expansion strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Expansion Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/gap-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/gap-analysis/SKILL.md new file mode 100644 index 0000000..7ef8d43 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/gap-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a gap analysis with structured process, quality checks, and system integration +--- + +# Gap Analysis + +## Purpose + +Analyze and produce a comprehensive gap analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gap analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gap analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gap analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Gap Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/implementation-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/implementation-roadmap/SKILL.md new file mode 100644 index 0000000..e1e9280 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/implementation-roadmap/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a implementation roadmap with structured process, quality checks, and system integration +--- + +# Implementation Roadmap + +## Purpose + +Design and document a comprehensive implementation roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing implementation roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the implementation roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the implementation roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Implementation Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/industry-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/industry-analysis/SKILL.md new file mode 100644 index 0000000..c5fcfb3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/industry-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a industry analysis with structured process, quality checks, and system integration +--- + +# Industry Analysis + +## Purpose + +Analyze and produce a comprehensive industry analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing industry analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the industry analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the industry analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Industry Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/innovation-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/innovation-strategy/SKILL.md new file mode 100644 index 0000000..5bf8e1d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/innovation-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a innovation strategy with structured process, quality checks, and system integration +--- + +# Innovation Strategy + +## Purpose + +Design and document a comprehensive innovation strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing innovation strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the innovation strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the innovation strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Innovation Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/integration-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/integration-planning/SKILL.md new file mode 100644 index 0000000..b3e861a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/integration-planning/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a integration planning with structured process, quality checks, and system integration +--- + +# Integration Planning + +## Purpose + +Design and document a comprehensive integration planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing integration planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the integration planning +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the integration planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Integration Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/journey-mapping/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/journey-mapping/SKILL.md new file mode 100644 index 0000000..7277b5c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/journey-mapping/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a journey mapping with structured process, quality checks, and system integration +--- + +# Journey Mapping + +## Purpose + +Create a comprehensive journey mapping that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing journey mapping documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the journey mapping +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the journey mapping using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Journey Mapping + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/knowledge-management/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/knowledge-management/SKILL.md new file mode 100644 index 0000000..5c84c3c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/knowledge-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a knowledge management with structured process, quality checks, and system integration +--- + +# Knowledge Management + +## Purpose + +Create a comprehensive knowledge management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing knowledge management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the knowledge management +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the knowledge management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Knowledge Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/lean-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/lean-assessment/SKILL.md new file mode 100644 index 0000000..5d2149b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/lean-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a lean assessment with structured process, quality checks, and system integration +--- + +# Lean Assessment + +## Purpose + +Analyze and produce a comprehensive lean assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lean assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lean assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lean assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Lean Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/market-entry-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/market-entry-strategy/SKILL.md new file mode 100644 index 0000000..c7f870e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/market-entry-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a market entry strategy with structured process, quality checks, and system integration +--- + +# Market Entry Strategy + +## Purpose + +Design and document a comprehensive market entry strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market entry strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market entry strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market entry strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Market Entry Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/market-landscape/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/market-landscape/SKILL.md new file mode 100644 index 0000000..13e173d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/market-landscape/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a market landscape with structured process, quality checks, and system integration +--- + +# Market Landscape + +## Purpose + +Create a comprehensive market landscape that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market landscape documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market landscape +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market landscape using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Market Landscape + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/maturity-model/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/maturity-model/SKILL.md new file mode 100644 index 0000000..507a9db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/maturity-model/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a maturity model with structured process, quality checks, and system integration +--- + +# Maturity Model + +## Purpose + +Design and document a comprehensive maturity model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing maturity model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the maturity model +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the maturity model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Maturity Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/operating-model/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/operating-model/SKILL.md new file mode 100644 index 0000000..c22c1e7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/operating-model/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a operating model with structured process, quality checks, and system integration +--- + +# Operating Model + +## Purpose + +Design and document a comprehensive operating model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing operating model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the operating model +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the operating model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Operating Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/organizational-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/organizational-assessment/SKILL.md new file mode 100644 index 0000000..425762f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/organizational-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a organizational assessment with structured process, quality checks, and system integration +--- + +# Organizational Assessment + +## Purpose + +Analyze and produce a comprehensive organizational assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing organizational assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the organizational assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the organizational assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Organizational Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/pestel-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/pestel-analysis/SKILL.md new file mode 100644 index 0000000..d3a9022 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/pestel-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a pestel analysis with structured process, quality checks, and system integration +--- + +# Pestel Analysis + +## Purpose + +Analyze and produce a comprehensive pestel analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pestel analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pestel analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pestel analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Pestel Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/porters-five-forces/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/porters-five-forces/SKILL.md new file mode 100644 index 0000000..fe66c50 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/porters-five-forces/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a porters five forces with structured process, quality checks, and system integration +--- + +# Porters Five Forces + +## Purpose + +Create a comprehensive porters five forces that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing porters five forces documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the porters five forces +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the porters five forces using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Porters Five Forces + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/post-merger-integration/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/post-merger-integration/SKILL.md new file mode 100644 index 0000000..7b38455 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/post-merger-integration/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a post merger integration with structured process, quality checks, and system integration +--- + +# Post Merger Integration + +## Purpose + +Create a comprehensive post merger integration that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing post merger integration documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the post merger integration +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the post merger integration using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Post Merger Integration + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/process-improvement/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/process-improvement/SKILL.md new file mode 100644 index 0000000..fbe6811 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/process-improvement/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a process improvement with structured process, quality checks, and system integration +--- + +# Process Improvement + +## Purpose + +Create a comprehensive process improvement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing process improvement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the process improvement +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the process improvement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Process Improvement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/recommendation-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/recommendation-deck/SKILL.md new file mode 100644 index 0000000..2308408 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/recommendation-deck/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a recommendation deck with structured process, quality checks, and system integration +--- + +# Recommendation Deck + +## Purpose + +Create a comprehensive recommendation deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recommendation deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recommendation deck +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recommendation deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Recommendation Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/red-team-exercise/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/red-team-exercise/SKILL.md new file mode 100644 index 0000000..45b9b4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/red-team-exercise/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a red team exercise with structured process, quality checks, and system integration +--- + +# Red Team Exercise + +## Purpose + +Create a comprehensive red team exercise that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing red team exercise documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the red team exercise +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the red team exercise using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Red Team Exercise + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/scenario-planning-consulting/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/scenario-planning-consulting/SKILL.md new file mode 100644 index 0000000..8b30f51 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/scenario-planning-consulting/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a scenario planning consulting with structured process, quality checks, and system integration +--- + +# Scenario Planning Consulting + +## Purpose + +Design and document a comprehensive scenario planning consulting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scenario planning consulting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scenario planning consulting +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scenario planning consulting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Scenario Planning Consulting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/scope-of-work/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/scope-of-work/SKILL.md new file mode 100644 index 0000000..773fac6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/scope-of-work/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a scope of work with structured process, quality checks, and system integration +--- + +# Scope Of Work + +## Purpose + +Create a comprehensive scope of work that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scope of work documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scope of work +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scope of work using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Scope Of Work + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/service-design/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/service-design/SKILL.md new file mode 100644 index 0000000..8c979c9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/service-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a service design with structured process, quality checks, and system integration +--- + +# Service Design + +## Purpose + +Create a comprehensive service design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing service design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the service design +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the service design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Service Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/shared-services/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/shared-services/SKILL.md new file mode 100644 index 0000000..7b67691 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/shared-services/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a shared services with structured process, quality checks, and system integration +--- + +# Shared Services + +## Purpose + +Create a comprehensive shared services that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing shared services documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the shared services +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the shared services using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Shared Services + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/six-sigma-project/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/six-sigma-project/SKILL.md new file mode 100644 index 0000000..f41df8c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/six-sigma-project/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a six sigma project with structured process, quality checks, and system integration +--- + +# Six Sigma Project + +## Purpose + +Create a comprehensive six sigma project that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing six sigma project documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the six sigma project +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the six sigma project using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Six Sigma Project + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/stakeholder-interview-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/stakeholder-interview-guide/SKILL.md new file mode 100644 index 0000000..0b5aaa0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/stakeholder-interview-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a stakeholder interview guide with structured process, quality checks, and system integration +--- + +# Stakeholder Interview Guide + +## Purpose + +Design and document a comprehensive stakeholder interview guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stakeholder interview guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stakeholder interview guide +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stakeholder interview guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Stakeholder Interview Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/strategy-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/strategy-framework/SKILL.md new file mode 100644 index 0000000..9afbb73 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/strategy-framework/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a strategy framework with structured process, quality checks, and system integration +--- + +# Strategy Framework + +## Purpose + +Design and document a comprehensive strategy framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing strategy framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the strategy framework +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the strategy framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Strategy Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/swot-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/swot-analysis/SKILL.md new file mode 100644 index 0000000..4a8fde7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/swot-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a swot analysis with structured process, quality checks, and system integration +--- + +# Swot Analysis + +## Purpose + +Analyze and produce a comprehensive swot analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing swot analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the swot analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the swot analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Swot Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/talent-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/talent-strategy/SKILL.md new file mode 100644 index 0000000..311ca25 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/talent-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a talent strategy with structured process, quality checks, and system integration +--- + +# Talent Strategy + +## Purpose + +Design and document a comprehensive talent strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing talent strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the talent strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the talent strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Talent Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/technology-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/technology-assessment/SKILL.md new file mode 100644 index 0000000..aa5333e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/technology-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a technology assessment with structured process, quality checks, and system integration +--- + +# Technology Assessment + +## Purpose + +Analyze and produce a comprehensive technology assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technology assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technology assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technology assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Technology Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/transformation-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/transformation-roadmap/SKILL.md new file mode 100644 index 0000000..5620364 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/transformation-roadmap/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a transformation roadmap with structured process, quality checks, and system integration +--- + +# Transformation Roadmap + +## Purpose + +Design and document a comprehensive transformation roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing transformation roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the transformation roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the transformation roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Transformation Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/trend-analysis-consulting/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/trend-analysis-consulting/SKILL.md new file mode 100644 index 0000000..70606ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/trend-analysis-consulting/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a trend analysis consulting with structured process, quality checks, and system integration +--- + +# Trend Analysis Consulting + +## Purpose + +Analyze and produce a comprehensive trend analysis consulting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trend analysis consulting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trend analysis consulting +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trend analysis consulting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Trend Analysis Consulting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/value-chain-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/value-chain-analysis/SKILL.md new file mode 100644 index 0000000..d930b5c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/value-chain-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a value chain analysis with structured process, quality checks, and system integration +--- + +# Value Chain Analysis + +## Purpose + +Analyze and produce a comprehensive value chain analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing value chain analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the value chain analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the value chain analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Value Chain Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/vendor-selection/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/vendor-selection/SKILL.md new file mode 100644 index 0000000..878fb5c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/vendor-selection/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a vendor selection with structured process, quality checks, and system integration +--- + +# Vendor Selection + +## Purpose + +Create a comprehensive vendor selection that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor selection documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor selection +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor selection using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# Vendor Selection + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/consulting/war-gaming/SKILL.md b/clowdex-download/.claude/.claude/skills/consulting/war-gaming/SKILL.md new file mode 100644 index 0000000..e838748 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/consulting/war-gaming/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a war gaming with structured process, quality checks, and system integration +--- + +# War Gaming + +## Purpose + +Create a comprehensive war gaming that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Consulting & Strategy + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing war gaming documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MECE (Mutually Exclusive, Collectively Exhaustive), Pyramid Principle, Issue Tree + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the war gaming +- Identify gaps, opportunities, and risks +- Define success metrics: Utilization Rate, Realization Rate, Client Satisfaction Score, Repeat Business Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the war gaming using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always start with the answer (Pyramid Principle) + +## Output Format + +```markdown +# War Gaming + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MECE (Mutually Exclusive, Collectively Exhaustive) +- Pyramid Principle +- Issue Tree +- Hypothesis-Driven Problem Solving +- 7S Framework +- Value Chain Analysis + +## Key Metrics +- Utilization Rate +- Realization Rate +- Client Satisfaction Score +- Repeat Business Rate +- Revenue Per Consultant +- Project Margin + +## Best Practices +- Always start with the answer (Pyramid Principle) +- One clear recommendation per deliverable +- Quantify impact in client terms ($, %, time) +- Weekly status updates without being asked +- Build internal champions at every level + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/about-page-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/about-page-copy/SKILL.md new file mode 100644 index 0000000..d075724 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/about-page-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a about page copy with structured process, quality checks, and system integration +--- + +# About Page Copy + +## Purpose + +Create a comprehensive about page copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing about page copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the about page copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the about page copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# About Page Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-facebook/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-facebook/SKILL.md new file mode 100644 index 0000000..3a471a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-facebook/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy facebook with structured process, quality checks, and system integration +--- + +# Ad Copy Facebook + +## Purpose + +Create a comprehensive ad copy facebook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy facebook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy facebook +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy facebook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Facebook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-google/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-google/SKILL.md new file mode 100644 index 0000000..91b65ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-google/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy google with structured process, quality checks, and system integration +--- + +# Ad Copy Google + +## Purpose + +Create a comprehensive ad copy google that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy google documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy google +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy google using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Google + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-linkedin/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-linkedin/SKILL.md new file mode 100644 index 0000000..5c0288a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-linkedin/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy linkedin with structured process, quality checks, and system integration +--- + +# Ad Copy Linkedin + +## Purpose + +Create a comprehensive ad copy linkedin that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy linkedin documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy linkedin +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy linkedin using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Linkedin + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-tiktok/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-tiktok/SKILL.md new file mode 100644 index 0000000..1811194 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-tiktok/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy tiktok with structured process, quality checks, and system integration +--- + +# Ad Copy Tiktok + +## Purpose + +Create a comprehensive ad copy tiktok that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy tiktok documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy tiktok +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy tiktok using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Tiktok + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-twitter/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-twitter/SKILL.md new file mode 100644 index 0000000..d03671f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-twitter/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy twitter with structured process, quality checks, and system integration +--- + +# Ad Copy Twitter + +## Purpose + +Create a comprehensive ad copy twitter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy twitter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy twitter +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy twitter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Twitter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ad-copy-youtube/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ad-copy-youtube/SKILL.md new file mode 100644 index 0000000..9851e20 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ad-copy-youtube/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ad copy youtube with structured process, quality checks, and system integration +--- + +# Ad Copy Youtube + +## Purpose + +Create a comprehensive ad copy youtube that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ad copy youtube documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ad copy youtube +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ad copy youtube using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ad Copy Youtube + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/annual-report-narrative/SKILL.md b/clowdex-download/.claude/.claude/skills/content/annual-report-narrative/SKILL.md new file mode 100644 index 0000000..69437ae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/annual-report-narrative/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a annual report narrative with structured process, quality checks, and system integration +--- + +# Annual Report Narrative + +## Purpose + +Analyze and produce a comprehensive annual report narrative that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing annual report narrative documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the annual report narrative +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the annual report narrative using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Annual Report Narrative + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/api-documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/content/api-documentation/SKILL.md new file mode 100644 index 0000000..a728494 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/api-documentation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a api documentation with structured process, quality checks, and system integration +--- + +# Api Documentation + +## Purpose + +Create a comprehensive api documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Api Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/blog-content-calendar/SKILL.md b/clowdex-download/.claude/.claude/skills/content/blog-content-calendar/SKILL.md new file mode 100644 index 0000000..3d9f6b8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/blog-content-calendar/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a blog content calendar with structured process, quality checks, and system integration +--- + +# Blog Content Calendar + +## Purpose + +Design and document a comprehensive blog content calendar that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing blog content calendar documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the blog content calendar +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the blog content calendar using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Blog Content Calendar + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/blog-post/SKILL.md b/clowdex-download/.claude/.claude/skills/content/blog-post/SKILL.md new file mode 100644 index 0000000..219f77e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/blog-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a blog post with structured process, quality checks, and system integration +--- + +# Blog Post + +## Purpose + +Create a comprehensive blog post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing blog post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the blog post +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the blog post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Blog Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/blog-series-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/content/blog-series-plan/SKILL.md new file mode 100644 index 0000000..b9c82a8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/blog-series-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a blog series plan with structured process, quality checks, and system integration +--- + +# Blog Series Plan + +## Purpose + +Design and document a comprehensive blog series plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing blog series plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the blog series plan +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the blog series plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Blog Series Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/brand-story/SKILL.md b/clowdex-download/.claude/.claude/skills/content/brand-story/SKILL.md new file mode 100644 index 0000000..7f5d279 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/brand-story/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a brand story with structured process, quality checks, and system integration +--- + +# Brand Story + +## Purpose + +Create a comprehensive brand story that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand story documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand story +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand story using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Brand Story + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/business-proposal-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/business-proposal-copy/SKILL.md new file mode 100644 index 0000000..da7d5e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/business-proposal-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a business proposal copy with structured process, quality checks, and system integration +--- + +# Business Proposal Copy + +## Purpose + +Create a comprehensive business proposal copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business proposal copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business proposal copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business proposal copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Business Proposal Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/byline-article/SKILL.md b/clowdex-download/.claude/.claude/skills/content/byline-article/SKILL.md new file mode 100644 index 0000000..623ef7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/byline-article/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a byline article with structured process, quality checks, and system integration +--- + +# Byline Article + +## Purpose + +Create a comprehensive byline article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing byline article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the byline article +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the byline article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Byline Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/case-study/SKILL.md b/clowdex-download/.claude/.claude/skills/content/case-study/SKILL.md new file mode 100644 index 0000000..969905e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/case-study/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a case study with structured process, quality checks, and system integration +--- + +# Case Study + +## Purpose + +Create a comprehensive case study that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing case study documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the case study +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the case study using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Case Study + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/changelog/SKILL.md b/clowdex-download/.claude/.claude/skills/content/changelog/SKILL.md new file mode 100644 index 0000000..789bd53 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/changelog/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a changelog with structured process, quality checks, and system integration +--- + +# Changelog + +## Purpose + +Create a comprehensive changelog that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing changelog documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the changelog +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the changelog using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Changelog + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/checkout-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/checkout-copy/SKILL.md new file mode 100644 index 0000000..3008c2b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/checkout-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a checkout copy with structured process, quality checks, and system integration +--- + +# Checkout Copy + +## Purpose + +Analyze and produce a comprehensive checkout copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing checkout copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the checkout copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the checkout copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Checkout Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/company-update/SKILL.md b/clowdex-download/.claude/.claude/skills/content/company-update/SKILL.md new file mode 100644 index 0000000..7f37505 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/company-update/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a company update with structured process, quality checks, and system integration +--- + +# Company Update + +## Purpose + +Create a comprehensive company update that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing company update documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the company update +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the company update using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Company Update + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/comparison-article/SKILL.md b/clowdex-download/.claude/.claude/skills/content/comparison-article/SKILL.md new file mode 100644 index 0000000..34ce063 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/comparison-article/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a comparison article with structured process, quality checks, and system integration +--- + +# Comparison Article + +## Purpose + +Analyze and produce a comprehensive comparison article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing comparison article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the comparison article +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the comparison article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Comparison Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/content-atomization/SKILL.md b/clowdex-download/.claude/.claude/skills/content/content-atomization/SKILL.md new file mode 100644 index 0000000..8b01c1a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/content-atomization/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a content atomization with structured process, quality checks, and system integration +--- + +# Content Atomization + +## Purpose + +Create a comprehensive content atomization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content atomization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content atomization +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content atomization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Content Atomization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/content-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/content/content-audit/SKILL.md new file mode 100644 index 0000000..c212eb4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/content-audit/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a content audit with structured process, quality checks, and system integration +--- + +# Content Audit + +## Purpose + +Analyze and produce a comprehensive content audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content audit +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Content Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/content-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/content/content-brief/SKILL.md new file mode 100644 index 0000000..2dc755e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/content-brief/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a content brief with structured process, quality checks, and system integration +--- + +# Content Brief + +## Purpose + +Create a comprehensive content brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content brief +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Content Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/content-gap-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/content/content-gap-analysis/SKILL.md new file mode 100644 index 0000000..d335584 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/content-gap-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a content gap analysis with structured process, quality checks, and system integration +--- + +# Content Gap Analysis + +## Purpose + +Analyze and produce a comprehensive content gap analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content gap analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content gap analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content gap analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Content Gap Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/content-repurposing/SKILL.md b/clowdex-download/.claude/.claude/skills/content/content-repurposing/SKILL.md new file mode 100644 index 0000000..10d3ce3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/content-repurposing/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a content repurposing with structured process, quality checks, and system integration +--- + +# Content Repurposing + +## Purpose + +Create a comprehensive content repurposing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content repurposing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content repurposing +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content repurposing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Content Repurposing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/cta-optimizer/SKILL.md b/clowdex-download/.claude/.claude/skills/content/cta-optimizer/SKILL.md new file mode 100644 index 0000000..d19f78e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/cta-optimizer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a cta optimizer with structured process, quality checks, and system integration +--- + +# Cta Optimizer + +## Purpose + +Create a comprehensive cta optimizer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cta optimizer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cta optimizer +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cta optimizer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Cta Optimizer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/customer-story/SKILL.md b/clowdex-download/.claude/.claude/skills/content/customer-story/SKILL.md new file mode 100644 index 0000000..f22d1e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/customer-story/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a customer story with structured process, quality checks, and system integration +--- + +# Customer Story + +## Purpose + +Create a comprehensive customer story that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer story documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer story +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer story using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Customer Story + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/content/documentation/SKILL.md new file mode 100644 index 0000000..bd9f577 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/documentation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a documentation with structured process, quality checks, and system integration +--- + +# Documentation + +## Purpose + +Create a comprehensive documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ebook-chapter/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ebook-chapter/SKILL.md new file mode 100644 index 0000000..c26af69 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ebook-chapter/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ebook chapter with structured process, quality checks, and system integration +--- + +# Ebook Chapter + +## Purpose + +Create a comprehensive ebook chapter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ebook chapter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ebook chapter +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ebook chapter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ebook Chapter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/ebook-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/content/ebook-outline/SKILL.md new file mode 100644 index 0000000..aab547b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/ebook-outline/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a ebook outline with structured process, quality checks, and system integration +--- + +# Ebook Outline + +## Purpose + +Create a comprehensive ebook outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ebook outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ebook outline +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ebook outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Ebook Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/elevator-pitch-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/elevator-pitch-copy/SKILL.md new file mode 100644 index 0000000..7b77b56 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/elevator-pitch-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a elevator pitch copy with structured process, quality checks, and system integration +--- + +# Elevator Pitch Copy + +## Purpose + +Create a comprehensive elevator pitch copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing elevator pitch copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the elevator pitch copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the elevator pitch copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Elevator Pitch Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/email-body-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/email-body-copy/SKILL.md new file mode 100644 index 0000000..bac2682 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/email-body-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a email body copy with structured process, quality checks, and system integration +--- + +# Email Body Copy + +## Purpose + +Create a comprehensive email body copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email body copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email body copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email body copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Email Body Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/email-sequence-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/email-sequence-copy/SKILL.md new file mode 100644 index 0000000..a87983f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/email-sequence-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a email sequence copy with structured process, quality checks, and system integration +--- + +# Email Sequence Copy + +## Purpose + +Create a comprehensive email sequence copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email sequence copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email sequence copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email sequence copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Email Sequence Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/email-subject-lines/SKILL.md b/clowdex-download/.claude/.claude/skills/content/email-subject-lines/SKILL.md new file mode 100644 index 0000000..230b1cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/email-subject-lines/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a email subject lines with structured process, quality checks, and system integration +--- + +# Email Subject Lines + +## Purpose + +Create a comprehensive email subject lines that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email subject lines documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email subject lines +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email subject lines using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Email Subject Lines + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/empty-state-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/empty-state-copy/SKILL.md new file mode 100644 index 0000000..554b7c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/empty-state-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a empty state copy with structured process, quality checks, and system integration +--- + +# Empty State Copy + +## Purpose + +Create a comprehensive empty state copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing empty state copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the empty state copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the empty state copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Empty State Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/error-message-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/error-message-copy/SKILL.md new file mode 100644 index 0000000..006d795 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/error-message-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a error message copy with structured process, quality checks, and system integration +--- + +# Error Message Copy + +## Purpose + +Create a comprehensive error message copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing error message copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the error message copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the error message copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Error Message Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/explainer-video-script/SKILL.md b/clowdex-download/.claude/.claude/skills/content/explainer-video-script/SKILL.md new file mode 100644 index 0000000..3218cb3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/explainer-video-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a explainer video script with structured process, quality checks, and system integration +--- + +# Explainer Video Script + +## Purpose + +Create a comprehensive explainer video script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing explainer video script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the explainer video script +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the explainer video script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Explainer Video Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/faq-page/SKILL.md b/clowdex-download/.claude/.claude/skills/content/faq-page/SKILL.md new file mode 100644 index 0000000..5a6f670 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/faq-page/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a faq page with structured process, quality checks, and system integration +--- + +# Faq Page + +## Purpose + +Create a comprehensive faq page that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing faq page documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the faq page +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the faq page using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Faq Page + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/feature-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/content/feature-comparison/SKILL.md new file mode 100644 index 0000000..18bf47e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/feature-comparison/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a feature comparison with structured process, quality checks, and system integration +--- + +# Feature Comparison + +## Purpose + +Analyze and produce a comprehensive feature comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature comparison +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Feature Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/grant-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/content/grant-proposal/SKILL.md new file mode 100644 index 0000000..abea6d6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/grant-proposal/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a grant proposal with structured process, quality checks, and system integration +--- + +# Grant Proposal + +## Purpose + +Create a comprehensive grant proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grant proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grant proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grant proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Grant Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/headline-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/content/headline-generator/SKILL.md new file mode 100644 index 0000000..57d3d56 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/headline-generator/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a headline generator with structured process, quality checks, and system integration +--- + +# Headline Generator + +## Purpose + +Create a comprehensive headline generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing headline generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the headline generator +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the headline generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Headline Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/homepage-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/homepage-copy/SKILL.md new file mode 100644 index 0000000..da251de --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/homepage-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a homepage copy with structured process, quality checks, and system integration +--- + +# Homepage Copy + +## Purpose + +Create a comprehensive homepage copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing homepage copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the homepage copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the homepage copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Homepage Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/how-to-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/content/how-to-guide/SKILL.md new file mode 100644 index 0000000..18c9ff5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/how-to-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a how to guide with structured process, quality checks, and system integration +--- + +# How To Guide + +## Purpose + +Design and document a comprehensive how to guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing how to guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the how to guide +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the how to guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# How To Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/in-app-message-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/in-app-message-copy/SKILL.md new file mode 100644 index 0000000..8f98e8e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/in-app-message-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a in app message copy with structured process, quality checks, and system integration +--- + +# In App Message Copy + +## Purpose + +Create a comprehensive in app message copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing in app message copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the in app message copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the in app message copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# In App Message Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/industry-report/SKILL.md b/clowdex-download/.claude/.claude/skills/content/industry-report/SKILL.md new file mode 100644 index 0000000..cfafc52 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/industry-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a industry report with structured process, quality checks, and system integration +--- + +# Industry Report + +## Purpose + +Analyze and produce a comprehensive industry report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing industry report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the industry report +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the industry report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Industry Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/investor-update/SKILL.md b/clowdex-download/.claude/.claude/skills/content/investor-update/SKILL.md new file mode 100644 index 0000000..29dc047 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/investor-update/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a investor update with structured process, quality checks, and system integration +--- + +# Investor Update + +## Purpose + +Create a comprehensive investor update that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor update documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor update +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor update using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Investor Update + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/keynote-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/content/keynote-outline/SKILL.md new file mode 100644 index 0000000..c7f6725 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/keynote-outline/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a keynote outline with structured process, quality checks, and system integration +--- + +# Keynote Outline + +## Purpose + +Create a comprehensive keynote outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing keynote outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the keynote outline +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the keynote outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Keynote Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/landing-page-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/landing-page-copy/SKILL.md new file mode 100644 index 0000000..0433877 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/landing-page-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a landing page copy with structured process, quality checks, and system integration +--- + +# Landing Page Copy + +## Purpose + +Create a comprehensive landing page copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing landing page copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the landing page copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the landing page copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Landing Page Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/listicle/SKILL.md b/clowdex-download/.claude/.claude/skills/content/listicle/SKILL.md new file mode 100644 index 0000000..85ee2b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/listicle/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a listicle with structured process, quality checks, and system integration +--- + +# Listicle + +## Purpose + +Create a comprehensive listicle that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing listicle documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the listicle +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the listicle using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Listicle + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/manifesto-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/content/manifesto-writer/SKILL.md new file mode 100644 index 0000000..c0d5a30 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/manifesto-writer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a manifesto writer with structured process, quality checks, and system integration +--- + +# Manifesto Writer + +## Purpose + +Create a comprehensive manifesto writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing manifesto writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the manifesto writer +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the manifesto writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Manifesto Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/media-advisory/SKILL.md b/clowdex-download/.claude/.claude/skills/content/media-advisory/SKILL.md new file mode 100644 index 0000000..589b0bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/media-advisory/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a media advisory with structured process, quality checks, and system integration +--- + +# Media Advisory + +## Purpose + +Create a comprehensive media advisory that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing media advisory documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the media advisory +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the media advisory using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Media Advisory + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/microcopy-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/content/microcopy-audit/SKILL.md new file mode 100644 index 0000000..31214b6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/microcopy-audit/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a microcopy audit with structured process, quality checks, and system integration +--- + +# Microcopy Audit + +## Purpose + +Analyze and produce a comprehensive microcopy audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing microcopy audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the microcopy audit +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the microcopy audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Microcopy Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/mission-statement/SKILL.md b/clowdex-download/.claude/.claude/skills/content/mission-statement/SKILL.md new file mode 100644 index 0000000..294c0ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/mission-statement/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a mission statement with structured process, quality checks, and system integration +--- + +# Mission Statement + +## Purpose + +Create a comprehensive mission statement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mission statement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mission statement +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mission statement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Mission Statement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/naming-brainstorm/SKILL.md b/clowdex-download/.claude/.claude/skills/content/naming-brainstorm/SKILL.md new file mode 100644 index 0000000..84f6cce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/naming-brainstorm/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a naming brainstorm with structured process, quality checks, and system integration +--- + +# Naming Brainstorm + +## Purpose + +Create a comprehensive naming brainstorm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing naming brainstorm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the naming brainstorm +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the naming brainstorm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Naming Brainstorm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/newsletter-issue/SKILL.md b/clowdex-download/.claude/.claude/skills/content/newsletter-issue/SKILL.md new file mode 100644 index 0000000..30b5908 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/newsletter-issue/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a newsletter issue with structured process, quality checks, and system integration +--- + +# Newsletter Issue + +## Purpose + +Create a comprehensive newsletter issue that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter issue documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter issue +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter issue using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Newsletter Issue + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/newsletter-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/newsletter-strategy/SKILL.md new file mode 100644 index 0000000..325ca12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/newsletter-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a newsletter strategy with structured process, quality checks, and system integration +--- + +# Newsletter Strategy + +## Purpose + +Design and document a comprehensive newsletter strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Newsletter Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/newsletter-welcome-series/SKILL.md b/clowdex-download/.claude/.claude/skills/content/newsletter-welcome-series/SKILL.md new file mode 100644 index 0000000..3a90f86 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/newsletter-welcome-series/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a newsletter welcome series with structured process, quality checks, and system integration +--- + +# Newsletter Welcome Series + +## Purpose + +Create a comprehensive newsletter welcome series that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter welcome series documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter welcome series +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter welcome series using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Newsletter Welcome Series + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/onboarding-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/onboarding-copy/SKILL.md new file mode 100644 index 0000000..d7b40a9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/onboarding-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a onboarding copy with structured process, quality checks, and system integration +--- + +# Onboarding Copy + +## Purpose + +Create a comprehensive onboarding copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Onboarding Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/opinion-piece/SKILL.md b/clowdex-download/.claude/.claude/skills/content/opinion-piece/SKILL.md new file mode 100644 index 0000000..4af058a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/opinion-piece/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a opinion piece with structured process, quality checks, and system integration +--- + +# Opinion Piece + +## Purpose + +Create a comprehensive opinion piece that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing opinion piece documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the opinion piece +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the opinion piece using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Opinion Piece + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/origin-story/SKILL.md b/clowdex-download/.claude/.claude/skills/content/origin-story/SKILL.md new file mode 100644 index 0000000..f91e141 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/origin-story/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a origin story with structured process, quality checks, and system integration +--- + +# Origin Story + +## Purpose + +Create a comprehensive origin story that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing origin story documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the origin story +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the origin story using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Origin Story + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/pillar-page/SKILL.md b/clowdex-download/.claude/.claude/skills/content/pillar-page/SKILL.md new file mode 100644 index 0000000..4e4fdbd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/pillar-page/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a pillar page with structured process, quality checks, and system integration +--- + +# Pillar Page + +## Purpose + +Create a comprehensive pillar page that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pillar page documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pillar page +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pillar page using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Pillar Page + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/podcast-episode-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/content/podcast-episode-plan/SKILL.md new file mode 100644 index 0000000..b572f4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/podcast-episode-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a podcast episode plan with structured process, quality checks, and system integration +--- + +# Podcast Episode Plan + +## Purpose + +Design and document a comprehensive podcast episode plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast episode plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast episode plan +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast episode plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Podcast Episode Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/podcast-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/content/podcast-outline/SKILL.md new file mode 100644 index 0000000..e4cf415 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/podcast-outline/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a podcast outline with structured process, quality checks, and system integration +--- + +# Podcast Outline + +## Purpose + +Create a comprehensive podcast outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast outline +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Podcast Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/podcast-show-notes/SKILL.md b/clowdex-download/.claude/.claude/skills/content/podcast-show-notes/SKILL.md new file mode 100644 index 0000000..76135f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/podcast-show-notes/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a podcast show notes with structured process, quality checks, and system integration +--- + +# Podcast Show Notes + +## Purpose + +Create a comprehensive podcast show notes that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast show notes documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast show notes +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast show notes using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Podcast Show Notes + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/presentation-script/SKILL.md b/clowdex-download/.claude/.claude/skills/content/presentation-script/SKILL.md new file mode 100644 index 0000000..5c5cac2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/presentation-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a presentation script with structured process, quality checks, and system integration +--- + +# Presentation Script + +## Purpose + +Create a comprehensive presentation script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing presentation script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the presentation script +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the presentation script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Presentation Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/press-release-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/content/press-release-writer/SKILL.md new file mode 100644 index 0000000..63d99f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/press-release-writer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a press release writer with structured process, quality checks, and system integration +--- + +# Press Release Writer + +## Purpose + +Create a comprehensive press release writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing press release writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the press release writer +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the press release writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Press Release Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/pricing-page-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/pricing-page-copy/SKILL.md new file mode 100644 index 0000000..53fa593 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/pricing-page-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a pricing page copy with structured process, quality checks, and system integration +--- + +# Pricing Page Copy + +## Purpose + +Create a comprehensive pricing page copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing page copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing page copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing page copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Pricing Page Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/product-description/SKILL.md b/clowdex-download/.claude/.claude/skills/content/product-description/SKILL.md new file mode 100644 index 0000000..40cfab8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/product-description/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a product description with structured process, quality checks, and system integration +--- + +# Product Description + +## Purpose + +Create a comprehensive product description that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product description documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product description +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product description using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Product Description + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/product-page-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/product-page-copy/SKILL.md new file mode 100644 index 0000000..a332741 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/product-page-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a product page copy with structured process, quality checks, and system integration +--- + +# Product Page Copy + +## Purpose + +Create a comprehensive product page copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product page copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product page copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product page copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Product Page Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/push-notification-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/push-notification-copy/SKILL.md new file mode 100644 index 0000000..debd29c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/push-notification-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a push notification copy with structured process, quality checks, and system integration +--- + +# Push Notification Copy + +## Purpose + +Create a comprehensive push notification copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing push notification copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the push notification copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the push notification copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Push Notification Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/release-notes/SKILL.md b/clowdex-download/.claude/.claude/skills/content/release-notes/SKILL.md new file mode 100644 index 0000000..d9a5084 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/release-notes/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a release notes with structured process, quality checks, and system integration +--- + +# Release Notes + +## Purpose + +Create a comprehensive release notes that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing release notes documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the release notes +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the release notes using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Release Notes + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/rfp-response/SKILL.md b/clowdex-download/.claude/.claude/skills/content/rfp-response/SKILL.md new file mode 100644 index 0000000..6cc5e7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/rfp-response/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a rfp response with structured process, quality checks, and system integration +--- + +# Rfp Response + +## Purpose + +Create a comprehensive rfp response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rfp response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rfp response +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rfp response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Rfp Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/slogan-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/content/slogan-generator/SKILL.md new file mode 100644 index 0000000..4c90924 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/slogan-generator/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a slogan generator with structured process, quality checks, and system integration +--- + +# Slogan Generator + +## Purpose + +Create a comprehensive slogan generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing slogan generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the slogan generator +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the slogan generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Slogan Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/sms-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/sms-copy/SKILL.md new file mode 100644 index 0000000..f7f4a12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/sms-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a sms copy with structured process, quality checks, and system integration +--- + +# Sms Copy + +## Purpose + +Create a comprehensive sms copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sms copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sms copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sms copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Sms Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/social-proof-page/SKILL.md b/clowdex-download/.claude/.claude/skills/content/social-proof-page/SKILL.md new file mode 100644 index 0000000..a0a49ff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/social-proof-page/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social proof page with structured process, quality checks, and system integration +--- + +# Social Proof Page + +## Purpose + +Create a comprehensive social proof page that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social proof page documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social proof page +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social proof page using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Social Proof Page + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/speech-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/content/speech-writer/SKILL.md new file mode 100644 index 0000000..33186ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/speech-writer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a speech writer with structured process, quality checks, and system integration +--- + +# Speech Writer + +## Purpose + +Create a comprehensive speech writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing speech writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the speech writer +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the speech writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Speech Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/style-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/content/style-guide/SKILL.md new file mode 100644 index 0000000..cfee0a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/style-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a style guide with structured process, quality checks, and system integration +--- + +# Style Guide + +## Purpose + +Design and document a comprehensive style guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing style guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the style guide +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the style guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Style Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/tagline-brainstorm/SKILL.md b/clowdex-download/.claude/.claude/skills/content/tagline-brainstorm/SKILL.md new file mode 100644 index 0000000..563c8c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/tagline-brainstorm/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a tagline brainstorm with structured process, quality checks, and system integration +--- + +# Tagline Brainstorm + +## Purpose + +Create a comprehensive tagline brainstorm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tagline brainstorm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tagline brainstorm +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tagline brainstorm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Tagline Brainstorm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/technical-writing/SKILL.md b/clowdex-download/.claude/.claude/skills/content/technical-writing/SKILL.md new file mode 100644 index 0000000..ccb9a07 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/technical-writing/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a technical writing with structured process, quality checks, and system integration +--- + +# Technical Writing + +## Purpose + +Create a comprehensive technical writing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technical writing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technical writing +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technical writing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Technical Writing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/testimonial-request/SKILL.md b/clowdex-download/.claude/.claude/skills/content/testimonial-request/SKILL.md new file mode 100644 index 0000000..05761d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/testimonial-request/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a testimonial request with structured process, quality checks, and system integration +--- + +# Testimonial Request + +## Purpose + +Create a comprehensive testimonial request that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing testimonial request documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the testimonial request +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the testimonial request using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Testimonial Request + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/thought-leadership-article/SKILL.md b/clowdex-download/.claude/.claude/skills/content/thought-leadership-article/SKILL.md new file mode 100644 index 0000000..87bfc65 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/thought-leadership-article/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a thought leadership article with structured process, quality checks, and system integration +--- + +# Thought Leadership Article + +## Purpose + +Create a comprehensive thought leadership article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing thought leadership article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the thought leadership article +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the thought leadership article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Thought Leadership Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/tone-of-voice-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/content/tone-of-voice-guide/SKILL.md new file mode 100644 index 0000000..37fb240 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/tone-of-voice-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a tone of voice guide with structured process, quality checks, and system integration +--- + +# Tone Of Voice Guide + +## Purpose + +Design and document a comprehensive tone of voice guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tone of voice guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tone of voice guide +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tone of voice guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Tone Of Voice Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/tutorial-script/SKILL.md b/clowdex-download/.claude/.claude/skills/content/tutorial-script/SKILL.md new file mode 100644 index 0000000..0ab26e9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/tutorial-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a tutorial script with structured process, quality checks, and system integration +--- + +# Tutorial Script + +## Purpose + +Create a comprehensive tutorial script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tutorial script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tutorial script +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tutorial script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Tutorial Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/user-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/content/user-guide/SKILL.md new file mode 100644 index 0000000..aa95013 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/user-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a user guide with structured process, quality checks, and system integration +--- + +# User Guide + +## Purpose + +Design and document a comprehensive user guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user guide +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# User Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/value-proposition-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/content/value-proposition-copy/SKILL.md new file mode 100644 index 0000000..6d2261b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/value-proposition-copy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a value proposition copy with structured process, quality checks, and system integration +--- + +# Value Proposition Copy + +## Purpose + +Create a comprehensive value proposition copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing value proposition copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the value proposition copy +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the value proposition copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Value Proposition Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/video-script/SKILL.md b/clowdex-download/.claude/.claude/skills/content/video-script/SKILL.md new file mode 100644 index 0000000..59577c1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/video-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a video script with structured process, quality checks, and system integration +--- + +# Video Script + +## Purpose + +Create a comprehensive video script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing video script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the video script +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the video script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Video Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/vision-statement/SKILL.md b/clowdex-download/.claude/.claude/skills/content/vision-statement/SKILL.md new file mode 100644 index 0000000..2b0e437 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/vision-statement/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a vision statement with structured process, quality checks, and system integration +--- + +# Vision Statement + +## Purpose + +Create a comprehensive vision statement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vision statement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vision statement +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vision statement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Vision Statement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/content/whitepaper/SKILL.md b/clowdex-download/.claude/.claude/skills/content/whitepaper/SKILL.md new file mode 100644 index 0000000..95a3600 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/content/whitepaper/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a whitepaper with structured process, quality checks, and system integration +--- + +# Whitepaper + +## Purpose + +Create a comprehensive whitepaper that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Content & Copywriting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing whitepaper documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA for copy, PAS (Problem-Agitate-Solve), BAB (Before-After-Bridge) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the whitepaper +- Identify gaps, opportunities, and risks +- Define success metrics: Readability Score (Flesch-Kincaid 60+), Time on Page, Scroll Depth, Social Shares +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the whitepaper using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write at 8th grade reading level for general audiences + +## Output Format + +```markdown +# Whitepaper + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA for copy +- PAS (Problem-Agitate-Solve) +- BAB (Before-After-Bridge) +- Inverted Pyramid +- Hub and Spoke content model +- Content Atomization +- StoryBrand + +## Key Metrics +- Readability Score (Flesch-Kincaid 60+) +- Time on Page +- Scroll Depth +- Social Shares +- Backlinks Generated +- Conversion Rate from Content + +## Best Practices +- Write at 8th grade reading level for general audiences +- One idea per paragraph, max 3 sentences +- Front-load the value — answer the question in the first 100 words +- Use active voice (90%+ of sentences) +- Every piece needs a clear CTA + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/advocacy-program/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/advocacy-program/SKILL.md new file mode 100644 index 0000000..aa77cd4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/advocacy-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a advocacy program with structured process, quality checks, and system integration +--- + +# Advocacy Program + +## Purpose + +Design and document a comprehensive advocacy program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing advocacy program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the advocacy program +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the advocacy program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Advocacy Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/ai-support-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/ai-support-setup/SKILL.md new file mode 100644 index 0000000..eab9275 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/ai-support-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ai support setup with structured process, quality checks, and system integration +--- + +# Ai Support Setup + +## Purpose + +Design and document a comprehensive ai support setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ai support setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ai support setup +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ai support setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Ai Support Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/beta-tester-program/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/beta-tester-program/SKILL.md new file mode 100644 index 0000000..8810ad2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/beta-tester-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a beta tester program with structured process, quality checks, and system integration +--- + +# Beta Tester Program + +## Purpose + +Design and document a comprehensive beta tester program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing beta tester program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the beta tester program +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the beta tester program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Beta Tester Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/certification-program/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/certification-program/SKILL.md new file mode 100644 index 0000000..c9394f8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/certification-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a certification program with structured process, quality checks, and system integration +--- + +# Certification Program + +## Purpose + +Design and document a comprehensive certification program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing certification program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the certification program +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the certification program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Certification Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/champion-program/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/champion-program/SKILL.md new file mode 100644 index 0000000..1eef332 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/champion-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a champion program with structured process, quality checks, and system integration +--- + +# Champion Program + +## Purpose + +Design and document a comprehensive champion program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing champion program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the champion program +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the champion program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Champion Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/chatbot-conversation-design/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/chatbot-conversation-design/SKILL.md new file mode 100644 index 0000000..c89776a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/chatbot-conversation-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a chatbot conversation design with structured process, quality checks, and system integration +--- + +# Chatbot Conversation Design + +## Purpose + +Create a comprehensive chatbot conversation design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chatbot conversation design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chatbot conversation design +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chatbot conversation design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Chatbot Conversation Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/chatbot-decision-tree/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/chatbot-decision-tree/SKILL.md new file mode 100644 index 0000000..8447097 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/chatbot-decision-tree/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a chatbot decision tree with structured process, quality checks, and system integration +--- + +# Chatbot Decision Tree + +## Purpose + +Create a comprehensive chatbot decision tree that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chatbot decision tree documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chatbot decision tree +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chatbot decision tree using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Chatbot Decision Tree + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/churn-prevention-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/churn-prevention-playbook/SKILL.md new file mode 100644 index 0000000..183139d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/churn-prevention-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a churn prevention playbook with structured process, quality checks, and system integration +--- + +# Churn Prevention Playbook + +## Purpose + +Design and document a comprehensive churn prevention playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing churn prevention playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the churn prevention playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the churn prevention playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Churn Prevention Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/churn-risk-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/churn-risk-analysis/SKILL.md new file mode 100644 index 0000000..3cca2e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/churn-risk-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a churn risk analysis with structured process, quality checks, and system integration +--- + +# Churn Risk Analysis + +## Purpose + +Analyze and produce a comprehensive churn risk analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing churn risk analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the churn risk analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the churn risk analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Churn Risk Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/community-management/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/community-management/SKILL.md new file mode 100644 index 0000000..049073e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/community-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a community management with structured process, quality checks, and system integration +--- + +# Community Management + +## Purpose + +Create a comprehensive community management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing community management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the community management +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the community management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Community Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/cs-cadence-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/cs-cadence-plan/SKILL.md new file mode 100644 index 0000000..7dd59fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/cs-cadence-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a cs cadence plan with structured process, quality checks, and system integration +--- + +# Cs Cadence Plan + +## Purpose + +Design and document a comprehensive cs cadence plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cs cadence plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cs cadence plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cs cadence plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Cs Cadence Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/csat-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/csat-survey/SKILL.md new file mode 100644 index 0000000..db4a40a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/csat-survey/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a csat survey with structured process, quality checks, and system integration +--- + +# Csat Survey + +## Purpose + +Create a comprehensive csat survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing csat survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the csat survey +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the csat survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Csat Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-advisory-board/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-advisory-board/SKILL.md new file mode 100644 index 0000000..a3bff91 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-advisory-board/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer advisory board with structured process, quality checks, and system integration +--- + +# Customer Advisory Board + +## Purpose + +Create a comprehensive customer advisory board that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer advisory board documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer advisory board +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer advisory board using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Advisory Board + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-communication-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-communication-plan/SKILL.md new file mode 100644 index 0000000..6c928cd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-communication-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a customer communication plan with structured process, quality checks, and system integration +--- + +# Customer Communication Plan + +## Purpose + +Design and document a comprehensive customer communication plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer communication plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer communication plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer communication plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Communication Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-effort-score/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-effort-score/SKILL.md new file mode 100644 index 0000000..7015b72 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-effort-score/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer effort score with structured process, quality checks, and system integration +--- + +# Customer Effort Score + +## Purpose + +Create a comprehensive customer effort score that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer effort score documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer effort score +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer effort score using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Effort Score + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-feedback-loop/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-feedback-loop/SKILL.md new file mode 100644 index 0000000..f0c3739 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-feedback-loop/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer feedback loop with structured process, quality checks, and system integration +--- + +# Customer Feedback Loop + +## Purpose + +Create a comprehensive customer feedback loop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer feedback loop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer feedback loop +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer feedback loop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Feedback Loop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-health-score/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-health-score/SKILL.md new file mode 100644 index 0000000..34018ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-health-score/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer health score with structured process, quality checks, and system integration +--- + +# Customer Health Score + +## Purpose + +Create a comprehensive customer health score that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer health score documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer health score +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer health score using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Health Score + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-journey-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-journey-optimization/SKILL.md new file mode 100644 index 0000000..6a6db17 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-journey-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer journey optimization with structured process, quality checks, and system integration +--- + +# Customer Journey Optimization + +## Purpose + +Create a comprehensive customer journey optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer journey optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer journey optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer journey optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Journey Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-onboarding-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-onboarding-plan/SKILL.md new file mode 100644 index 0000000..14491b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-onboarding-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a customer onboarding plan with structured process, quality checks, and system integration +--- + +# Customer Onboarding Plan + +## Purpose + +Design and document a comprehensive customer onboarding plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer onboarding plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer onboarding plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer onboarding plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Onboarding Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-success-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-success-playbook/SKILL.md new file mode 100644 index 0000000..abe5cfb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-success-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a customer success playbook with structured process, quality checks, and system integration +--- + +# Customer Success Playbook + +## Purpose + +Design and document a comprehensive customer success playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer success playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer success playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer success playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Success Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-training-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-training-plan/SKILL.md new file mode 100644 index 0000000..0d26413 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-training-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a customer training plan with structured process, quality checks, and system integration +--- + +# Customer Training Plan + +## Purpose + +Design and document a comprehensive customer training plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer training plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer training plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer training plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Training Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/customer-welcome-kit/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/customer-welcome-kit/SKILL.md new file mode 100644 index 0000000..2f0ffa9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/customer-welcome-kit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer welcome kit with structured process, quality checks, and system integration +--- + +# Customer Welcome Kit + +## Purpose + +Create a comprehensive customer welcome kit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer welcome kit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer welcome kit +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer welcome kit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Customer Welcome Kit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/escalation-procedure/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/escalation-procedure/SKILL.md new file mode 100644 index 0000000..3b7e47c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/escalation-procedure/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a escalation procedure with structured process, quality checks, and system integration +--- + +# Escalation Procedure + +## Purpose + +Create a comprehensive escalation procedure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing escalation procedure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the escalation procedure +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the escalation procedure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Escalation Procedure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/expansion-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/expansion-playbook/SKILL.md new file mode 100644 index 0000000..5a97204 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/expansion-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a expansion playbook with structured process, quality checks, and system integration +--- + +# Expansion Playbook + +## Purpose + +Design and document a comprehensive expansion playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing expansion playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the expansion playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the expansion playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Expansion Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/experience-mapping/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/experience-mapping/SKILL.md new file mode 100644 index 0000000..3dd70bc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/experience-mapping/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a experience mapping with structured process, quality checks, and system integration +--- + +# Experience Mapping + +## Purpose + +Create a comprehensive experience mapping that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing experience mapping documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the experience mapping +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the experience mapping using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Experience Mapping + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/feature-announcement/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/feature-announcement/SKILL.md new file mode 100644 index 0000000..9ee9492 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/feature-announcement/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a feature announcement with structured process, quality checks, and system integration +--- + +# Feature Announcement + +## Purpose + +Create a comprehensive feature announcement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature announcement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature announcement +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature announcement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Feature Announcement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/feedback-categorization/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/feedback-categorization/SKILL.md new file mode 100644 index 0000000..f65cd05 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/feedback-categorization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a feedback categorization with structured process, quality checks, and system integration +--- + +# Feedback Categorization + +## Purpose + +Create a comprehensive feedback categorization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feedback categorization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feedback categorization +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feedback categorization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Feedback Categorization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/forum-moderation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/forum-moderation-guide/SKILL.md new file mode 100644 index 0000000..885a66b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/forum-moderation-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a forum moderation guide with structured process, quality checks, and system integration +--- + +# Forum Moderation Guide + +## Purpose + +Design and document a comprehensive forum moderation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing forum moderation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the forum moderation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the forum moderation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Forum Moderation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/friction-point-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/friction-point-analysis/SKILL.md new file mode 100644 index 0000000..9052508 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/friction-point-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a friction point analysis with structured process, quality checks, and system integration +--- + +# Friction Point Analysis + +## Purpose + +Analyze and produce a comprehensive friction point analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing friction point analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the friction point analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the friction point analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Friction Point Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/help-center-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/help-center-structure/SKILL.md new file mode 100644 index 0000000..4a5fcd0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/help-center-structure/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a help center structure with structured process, quality checks, and system integration +--- + +# Help Center Structure + +## Purpose + +Create a comprehensive help center structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing help center structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the help center structure +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the help center structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Help Center Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/implementation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/implementation-plan/SKILL.md new file mode 100644 index 0000000..a592a2c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/implementation-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a implementation plan with structured process, quality checks, and system integration +--- + +# Implementation Plan + +## Purpose + +Design and document a comprehensive implementation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing implementation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the implementation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the implementation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Implementation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/knowledge-base-article-support/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/knowledge-base-article-support/SKILL.md new file mode 100644 index 0000000..b33e073 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/knowledge-base-article-support/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a knowledge base article support with structured process, quality checks, and system integration +--- + +# Knowledge Base Article Support + +## Purpose + +Create a comprehensive knowledge base article support that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing knowledge base article support documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the knowledge base article support +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the knowledge base article support using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Knowledge Base Article Support + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/nps-survey-design/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/nps-survey-design/SKILL.md new file mode 100644 index 0000000..2e88358 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/nps-survey-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a nps survey design with structured process, quality checks, and system integration +--- + +# Nps Survey Design + +## Purpose + +Create a comprehensive nps survey design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nps survey design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nps survey design +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nps survey design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Nps Survey Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/outage-communication/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/outage-communication/SKILL.md new file mode 100644 index 0000000..2958547 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/outage-communication/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a outage communication with structured process, quality checks, and system integration +--- + +# Outage Communication + +## Purpose + +Create a comprehensive outage communication that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing outage communication documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the outage communication +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the outage communication using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Outage Communication + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/qbr-template/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/qbr-template/SKILL.md new file mode 100644 index 0000000..b81fa22 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/qbr-template/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a qbr template with structured process, quality checks, and system integration +--- + +# Qbr Template + +## Purpose + +Create a comprehensive qbr template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing qbr template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the qbr template +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the qbr template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Qbr Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/quality-assurance-support/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/quality-assurance-support/SKILL.md new file mode 100644 index 0000000..02045c1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/quality-assurance-support/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a quality assurance support with structured process, quality checks, and system integration +--- + +# Quality Assurance Support + +## Purpose + +Create a comprehensive quality assurance support that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quality assurance support documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quality assurance support +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quality assurance support using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Quality Assurance Support + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/renewal-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/renewal-playbook/SKILL.md new file mode 100644 index 0000000..033c4c6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/renewal-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a renewal playbook with structured process, quality checks, and system integration +--- + +# Renewal Playbook + +## Purpose + +Design and document a comprehensive renewal playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing renewal playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the renewal playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the renewal playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Renewal Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/response-time-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/response-time-analysis/SKILL.md new file mode 100644 index 0000000..95aa37d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/response-time-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a response time analysis with structured process, quality checks, and system integration +--- + +# Response Time Analysis + +## Purpose + +Analyze and produce a comprehensive response time analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing response time analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the response time analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the response time analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Response Time Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/self-service-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/self-service-strategy/SKILL.md new file mode 100644 index 0000000..a760ad3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/self-service-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a self service strategy with structured process, quality checks, and system integration +--- + +# Self Service Strategy + +## Purpose + +Design and document a comprehensive self service strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing self service strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the self service strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the self service strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Self Service Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/sla-definition/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/sla-definition/SKILL.md new file mode 100644 index 0000000..b91bd24 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/sla-definition/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a sla definition with structured process, quality checks, and system integration +--- + +# Sla Definition + +## Purpose + +Create a comprehensive sla definition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sla definition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sla definition +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sla definition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Sla Definition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/support-metrics-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/support-metrics-dashboard/SKILL.md new file mode 100644 index 0000000..a89c386 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/support-metrics-dashboard/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a support metrics dashboard with structured process, quality checks, and system integration +--- + +# Support Metrics Dashboard + +## Purpose + +Analyze and produce a comprehensive support metrics dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing support metrics dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the support metrics dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the support metrics dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Support Metrics Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/support-retrospective/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/support-retrospective/SKILL.md new file mode 100644 index 0000000..eefe887 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/support-retrospective/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a support retrospective with structured process, quality checks, and system integration +--- + +# Support Retrospective + +## Purpose + +Create a comprehensive support retrospective that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing support retrospective documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the support retrospective +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the support retrospective using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Support Retrospective + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/support-team-training/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/support-team-training/SKILL.md new file mode 100644 index 0000000..bc80761 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/support-team-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a support team training with structured process, quality checks, and system integration +--- + +# Support Team Training + +## Purpose + +Create a comprehensive support team training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing support team training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the support team training +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the support team training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Support Team Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/support-ticket-template/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/support-ticket-template/SKILL.md new file mode 100644 index 0000000..6b80da3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/support-ticket-template/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a support ticket template with structured process, quality checks, and system integration +--- + +# Support Ticket Template + +## Purpose + +Create a comprehensive support ticket template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing support ticket template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the support ticket template +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the support ticket template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Support Ticket Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/tier-support-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/tier-support-guide/SKILL.md new file mode 100644 index 0000000..e973830 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/tier-support-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a tier support guide with structured process, quality checks, and system integration +--- + +# Tier Support Guide + +## Purpose + +Design and document a comprehensive tier support guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tier support guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tier support guide +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tier support guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Tier Support Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/user-group-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/user-group-plan/SKILL.md new file mode 100644 index 0000000..dceca0a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/user-group-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a user group plan with structured process, quality checks, and system integration +--- + +# User Group Plan + +## Purpose + +Design and document a comprehensive user group plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user group plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user group plan +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user group plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# User Group Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/voice-of-customer/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/voice-of-customer/SKILL.md new file mode 100644 index 0000000..37259f1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/voice-of-customer/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a voice of customer with structured process, quality checks, and system integration +--- + +# Voice Of Customer + +## Purpose + +Create a comprehensive voice of customer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing voice of customer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the voice of customer +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the voice of customer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Voice Of Customer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/customer-success/webinar-series/SKILL.md b/clowdex-download/.claude/.claude/skills/customer-success/webinar-series/SKILL.md new file mode 100644 index 0000000..a15dbca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/customer-success/webinar-series/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a webinar series with structured process, quality checks, and system integration +--- + +# Webinar Series + +## Purpose + +Create a comprehensive webinar series that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Customer Success & Support + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing webinar series documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Customer Health Score, Customer Maturity Model, TSIA Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the webinar series +- Identify gaps, opportunities, and risks +- Define success metrics: Net Revenue Retention, Gross Revenue Retention, Customer Health Score, Time to First Value +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the webinar series using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Proactive outreach when health score drops + +## Output Format + +```markdown +# Webinar Series + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Customer Health Score +- Customer Maturity Model +- TSIA Framework +- Gainsight Playbooks +- Customer Lifecycle + +## Key Metrics +- Net Revenue Retention +- Gross Revenue Retention +- Customer Health Score +- Time to First Value +- Expansion Revenue +- NPS/CSAT/CES +- Logo Churn Rate + +## Best Practices +- Proactive outreach when health score drops +- QBRs with strategic accounts quarterly +- Onboarding complete within 30 days +- Document every customer interaction +- Celebrate customer wins publicly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/access-control-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/access-control-matrix/SKILL.md new file mode 100644 index 0000000..0b9df0e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/access-control-matrix/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a access control matrix with structured process, quality checks, and system integration +--- + +# Access Control Matrix + +## Purpose + +Create a comprehensive access control matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing access control matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-53 (AC-2, AC-3), RBAC, ABAC + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the access control matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Role Count, Permission Count per Role, Least Privilege Score, Role Overlap % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the access control matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define roles based on job functions — not individual permission sets + +## Output Format + +```markdown +# Access Control Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-53 (AC-2, AC-3) +- RBAC (Role-Based Access Control) +- ABAC (Attribute-Based Access Control) +- ISO 27001 (A.5.15) +- Principle of Least Privilege + +## Key Metrics +- Role Count +- Permission Count per Role +- Least Privilege Score +- Role Overlap % +- Access Exception Count +- Segregation of Duties Compliance + +## Best Practices +- Define roles based on job functions — not individual permission sets +- Validate least privilege: Can this role function with fewer permissions? +- Document role-to-permission mapping for every system in scope +- Flag any role with more than 20 permissions for review +- Review the matrix when organizational structure changes + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/api-security-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/api-security-assessment/SKILL.md new file mode 100644 index 0000000..28fe02f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/api-security-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a api security assessment with structured process, quality checks, and system integration +--- + +# API Security Assessment + +## Purpose + +Create a comprehensive api security assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api security assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP API Security Top 10, OpenAPI Specification Security Schemes, OAuth 2.0/OIDC + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api security assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Vulnerability Count per API, Authentication Bypass Attempts, Authorization Test Coverage, Rate Limiting Effectiveness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api security assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test against all OWASP API Security Top 10 categories + +## Output Format + +```markdown +# API Security Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP API Security Top 10 +- OpenAPI Specification Security Schemes +- OAuth 2.0/OIDC +- NIST SP 800-204 (Microservices Security) +- CIS API Security Benchmark + +## Key Metrics +- Vulnerability Count per API +- Authentication Bypass Attempts +- Authorization Test Coverage +- Rate Limiting Effectiveness +- Data Exposure Finding Count +- JWT Implementation Score + +## Best Practices +- Test against all OWASP API Security Top 10 categories +- Validate object-level authorization (BOLA) — the #1 API vulnerability +- Test rate limiting under load — misconfigured limits enable abuse +- Check for excessive data exposure in API responses (return only required fields) +- Validate JWT implementation: signature verification, expiry enforcement, audience restrictions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/attack-surface-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/attack-surface-analysis/SKILL.md new file mode 100644 index 0000000..dac9888 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/attack-surface-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create an attack surface analysis with structured process, quality checks, and system integration +--- + +# Attack Surface Analysis + +## Purpose + +Create a comprehensive attack surface analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing attack surface analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP Attack Surface Analysis, NIST SP 800-53 (RA-5), CIS Controls v8.1 (Controls 1, 2, 7) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the attack surface analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Total External Assets Discovered, Shadow IT Count, Exposed Services/Ports, Certificate Expiration Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the attack surface analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Discover assets from external perspective first — internal inventories are always incomplete + +## Output Format + +```markdown +# Attack Surface Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP Attack Surface Analysis +- NIST SP 800-53 (RA-5) +- CIS Controls v8.1 (Controls 1, 2, 7) +- External Attack Surface Management (EASM) +- MITRE ATT&CK (Reconnaissance) +- CISA Asset Discovery Guidance + +## Key Metrics +- Total External Assets Discovered +- Shadow IT Count +- Exposed Services/Ports +- Certificate Expiration Count +- Domain/Subdomain Count +- Unmanaged Asset Ratio +- Asset Discovery Delta (vs. CMDB) + +## Best Practices +- Discover assets from external perspective first — internal inventories are always incomplete +- Include cloud resources, SaaS instances, and shadow IT in the scope +- Monitor certificate expiry — expired certs indicate unmaintained assets +- Enumerate subdomains using DNS brute-force, certificate transparency logs, and passive DNS +- Rescan at least monthly — attack surfaces change continuously + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/backup-validation-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/backup-validation-report/SKILL.md new file mode 100644 index 0000000..9d56830 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/backup-validation-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a backup & recovery validation report with structured process, quality checks, and system integration +--- + +# Backup & Recovery Validation Report + +## Purpose + +Create a comprehensive backup & recovery validation report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing backup & recovery validation report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-34, ISO 27001 (A.8.13), CIS Controls v8.1 (Control 11) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the backup & recovery validation report +- Identify gaps, opportunities, and risks +- Define success metrics: Backup Success Rate (%), Restore Test Pass Rate, RTO Achievement in Tests, RPO Achievement in Tests +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the backup & recovery validation report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test restore procedures monthly — untested backups are unverified assumptions + +## Output Format + +```markdown +# Backup & Recovery Validation Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-34 +- ISO 27001 (A.8.13) +- CIS Controls v8.1 (Control 11) +- 3-2-1 Backup Rule +- Veeam/Commvault Best Practices + +## Key Metrics +- Backup Success Rate (%) +- Restore Test Pass Rate +- RTO Achievement in Tests +- RPO Achievement in Tests +- Backup Coverage (% of critical systems) +- Immutable Backup Percentage + +## Best Practices +- Test restore procedures monthly — backups that have not been restored are unverified +- Follow the 3-2-1 rule: 3 copies, 2 different media, 1 offsite +- Include immutable backup copies for ransomware resilience +- Validate data integrity after restore — not just file presence +- Monitor backup job failures daily with automated alerting + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/bcp/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/bcp/SKILL.md new file mode 100644 index 0000000..e1d59f5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/bcp/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a business continuity plan with structured process, quality checks, and system integration +--- + +# Business Continuity Plan + +## Purpose + +Create a comprehensive business continuity plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business continuity plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO 22301, NIST SP 800-34, BCI Good Practice Guidelines + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business continuity plan +- Identify gaps, opportunities, and risks +- Define success metrics: Business Impact Analysis Completeness, RTO Achievement Rate, RPO Achievement Rate, Plan Test Frequency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business continuity plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with a Business Impact Analysis (BIA) + +## Output Format + +```markdown +# Business Continuity Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO 22301 +- NIST SP 800-34 +- BCI Good Practice Guidelines +- DRII Professional Practices +- FFIEC IT Examination Handbook (BCP) + +## Key Metrics +- Business Impact Analysis Completeness +- RTO Achievement Rate +- RPO Achievement Rate +- Plan Test Frequency +- Recovery Team Readiness Score +- Third-Party Dependency Coverage + +## Best Practices +- Start with a Business Impact Analysis (BIA) — identify critical processes and acceptable downtime +- Define RTO/RPO for every critical process with business owner sign-off +- Maintain alternate communication channels for crisis coordination +- Test the plan annually with realistic scenarios — untested plans are hypothetical +- Include supply chain and third-party dependency recovery procedures + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/board-security-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/board-security-report/SKILL.md new file mode 100644 index 0000000..f0d3d60 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/board-security-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a executive/board security report with structured process, quality checks, and system integration +--- + +# Executive/Board Security Report + +## Purpose + +Create a comprehensive executive/board security report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive/board security report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NACD Cyber-Risk Oversight, SEC Cybersecurity Disclosure Rules, NIST CSF 2.0 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive/board security report +- Identify gaps, opportunities, and risks +- Define success metrics: Overall Cyber Risk Score, NIST CSF Maturity Rating, Incident Count and Trend, Security Investment ROI +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive/board security report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Lead with business risk, not technical jargon — boards care about impact + +## Output Format + +```markdown +# Executive/Board Security Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NACD Director Handbook on Cyber-Risk Oversight +- SEC Cybersecurity Disclosure Rules +- NIST CSF 2.0 (Governance) +- FAIR Risk Quantification +- World Economic Forum Cyber Risk Framework + +## Key Metrics +- Overall Cyber Risk Score +- NIST CSF Maturity Rating +- Incident Count and Trend +- Security Investment ROI +- Compliance Status Summary +- Benchmark Comparison + +## Best Practices +- Lead with business risk, not technical jargon — boards care about impact, not CVEs +- Present 3-5 key risk indicators with trend lines, not exhaustive control lists +- Quantify cyber risk in financial terms using FAIR methodology +- Include competitive benchmarking where available +- Keep the report to 5-7 slides — detail goes in appendices + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/cloud-security-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/cloud-security-assessment/SKILL.md new file mode 100644 index 0000000..3006295 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/cloud-security-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a cloud security assessment with structured process, quality checks, and system integration +--- + +# Cloud Security Assessment + +## Purpose + +Create a comprehensive cloud security assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cloud security assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CIS Benchmarks, CSA Cloud Controls Matrix, AWS Well-Architected Security Pillar + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cloud security assessment +- Identify gaps, opportunities, and risks +- Define success metrics: CIS Benchmark Compliance %, IAM Misconfigurations Count, Public Exposure Count, Encryption Coverage % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cloud security assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Assess against provider-specific CIS Benchmarks, not generic checklists + +## Output Format + +```markdown +# Cloud Security Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CIS Benchmarks (AWS/Azure/GCP) +- CSA Cloud Controls Matrix (CCM) +- NIST SP 800-144 +- AWS Well-Architected Security Pillar +- Shared Responsibility Model +- ISO 27017 (Cloud Security) + +## Key Metrics +- CIS Benchmark Compliance % +- IAM Misconfigurations Count +- Public Exposure Count (open S3/storage) +- Encryption Coverage % +- Security Group Rule Violations +- CloudTrail/Logging Coverage % +- Cross-Account Access Count + +## Best Practices +- Assess against provider-specific CIS Benchmarks (not generic checklists) +- Map shared responsibility boundaries explicitly for each service used +- Check for publicly exposed storage (S3 buckets, Azure blobs, GCS) — #1 cloud breach cause +- Validate IAM policies for least privilege — flag wildcard (*) permissions +- Review CloudTrail/Activity Logs for monitoring gaps + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/compliance-gap-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/compliance-gap-analysis/SKILL.md new file mode 100644 index 0000000..22abf57 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/compliance-gap-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a compliance gap analysis with structured process, quality checks, and system integration +--- + +# Compliance Gap Analysis + +## Purpose + +Create a comprehensive compliance gap analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance gap analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST CSF 2.0, CIS Controls v8.1, ISO 27001:2022 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance gap analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Control Implementation Rate, Gap Count by Priority, Estimated Remediation Effort, Compliance Score (%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance gap analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Assess current state objectively — self-assessments tend to overrate maturity + +## Output Format + +```markdown +# Compliance Gap Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST CSF 2.0 +- CIS Controls v8.1 +- ISO 27001:2022 +- PCI DSS 4.0 +- Unified Compliance Framework (UCF) + +## Key Metrics +- Control Implementation Rate (Implemented/Partial/Missing) +- Gap Count by Priority +- Estimated Remediation Effort (hours) +- Compliance Score (%) +- Time to Full Compliance +- Framework Coverage Overlap % + +## Best Practices +- Assess current state objectively — self-assessments tend to overrate maturity +- Map controls to multiple frameworks simultaneously to reduce duplicate effort +- Prioritize gaps by risk impact, not alphabetical control order +- Include effort estimates (hours/FTEs) and cost projections for each remediation +- Conduct gap analysis before selecting a compliance target, not after + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/data-breach-notification/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/data-breach-notification/SKILL.md new file mode 100644 index 0000000..9694af7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/data-breach-notification/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data breach notification package with structured process, quality checks, and system integration +--- + +# Data Breach Notification Package + +## Purpose + +Create a comprehensive data breach notification package that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data breach notification package documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GDPR Articles 33-34, US State Breach Notification Laws, HIPAA Breach Notification Rule + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data breach notification package +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Notification (vs. Deadline), Affected Individual Count, Notification Channel Effectiveness, Regulatory Inquiry Response Time +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data breach notification package using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Prepare templates in advance — you cannot draft notifications under incident pressure + +## Output Format + +```markdown +# Data Breach Notification Package + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GDPR Articles 33-34 +- US State Breach Notification Laws +- HIPAA Breach Notification Rule +- PCI DSS Incident Response +- APEC Privacy Framework + +## Key Metrics +- Time to Notification (vs. Regulatory Deadline) +- Affected Individual Count +- Notification Channel Effectiveness +- Regulatory Inquiry Response Time +- Remediation Offer Take-Up Rate +- Legal Review Completion Time + +## Best Practices +- Prepare templates in advance — you cannot draft notifications under incident pressure +- Map notification deadlines per jurisdiction: GDPR 72 hours, HIPAA 60 days, state laws vary +- Include legal review in the notification workflow before any external communication +- Offer concrete remediation (credit monitoring, password resets) — not just apologies +- Maintain a notification decision tree for risk to rights and freedoms assessment + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/data-classification-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/data-classification-policy/SKILL.md new file mode 100644 index 0000000..e9ff269 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/data-classification-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data classification policy & schema with structured process, quality checks, and system integration +--- + +# Data Classification Policy & Schema + +## Purpose + +Create a comprehensive data classification policy & schema that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data classification policy & schema documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO 27001 (A.5.12-13), NIST SP 800-60, FIPS 199 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data classification policy & schema +- Identify gaps, opportunities, and risks +- Define success metrics: Classification Coverage %, Labeling Compliance Rate, Handling Procedure Adherence, Misclassification Incident Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data classification policy & schema using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define 4 classification levels: Public, Internal, Confidential, Restricted + +## Output Format + +```markdown +# Data Classification Policy & Schema + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO 27001 (A.5.12-13) +- NIST SP 800-60 +- FIPS 199 +- CIS Controls v8.1 (Control 3) +- Data Governance Institute Framework + +## Key Metrics +- Classification Coverage (% of data assets classified) +- Labeling Compliance Rate +- Handling Procedure Adherence +- Misclassification Incident Count +- DLP Rule Coverage per Level +- Data Owner Assignment Rate + +## Best Practices +- Define 4 classification levels: Public, Internal, Confidential, Restricted +- Specify handling requirements per level (storage, transmission, access, disposal) +- Integrate classification labels with DLP tools for automated enforcement +- Train data owners on classification responsibility — IT cannot classify business data +- Review classifications annually — sensitivity changes as business context evolves + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/detection-rule/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/detection-rule/SKILL.md new file mode 100644 index 0000000..391056c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/detection-rule/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a detection rule / siem use case with structured process, quality checks, and system integration +--- + +# Detection Rule / SIEM Use Case + +## Purpose + +Create a comprehensive detection rule / siem use case that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing detection rule / siem use case documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Sigma Rules Standard, MITRE ATT&CK Detection, Splunk/Elastic/Sentinel Detection Frameworks + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the detection rule / siem use case +- Identify gaps, opportunities, and risks +- Define success metrics: True Positive Rate, False Positive Rate, Alert Volume per Rule, ATT&CK Technique Coverage +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the detection rule / siem use case using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Map every detection rule to a specific MITRE ATT&CK technique + +## Output Format + +```markdown +# Detection Rule / SIEM Use Case + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Sigma Rules Standard +- MITRE ATT&CK Detection +- Splunk/Elastic/Sentinel Detection Frameworks +- NIST SP 800-92 (Log Management) +- SOC-CMM Detection Engineering + +## Key Metrics +- True Positive Rate +- False Positive Rate +- Alert Volume per Rule +- ATT&CK Technique Coverage +- Mean Time from Rule Creation to Production +- Data Source Availability + +## Best Practices +- Map every detection rule to a specific MITRE ATT&CK technique +- Write rules in Sigma format first for portability across SIEM platforms +- Include tuning guidance — expected false positive sources and whitelist criteria +- Test rules against known-good and known-bad data before production deployment +- Document data source requirements — a rule without its data source is useless + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/disaster-recovery-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/disaster-recovery-plan/SKILL.md new file mode 100644 index 0000000..232cfdc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/disaster-recovery-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a disaster recovery plan with structured process, quality checks, and system integration +--- + +# Disaster Recovery Plan + +## Purpose + +Create a comprehensive disaster recovery plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing disaster recovery plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-34, ISO 22301, AWS/Azure/GCP DR Reference Architectures + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the disaster recovery plan +- Identify gaps, opportunities, and risks +- Define success metrics: RTO per System, RPO per System, DR Test Success Rate, Failover Time +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the disaster recovery plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Prioritize systems for recovery by BIA criticality + +## Output Format + +```markdown +# Disaster Recovery Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-34 +- ISO 22301 (Annex A) +- AWS/Azure/GCP DR Reference Architectures +- Tiered Recovery Strategy +- RPO/RTO Framework + +## Key Metrics +- RTO per System +- RPO per System +- DR Test Success Rate +- Failover Time +- Data Integrity Validation Score +- Geographic Separation Compliance + +## Best Practices +- Prioritize systems for recovery by BIA criticality — not all recover simultaneously +- Define recovery tiers: Tier 1 (0-4h), Tier 2 (4-24h), Tier 3 (24-72h) +- Automate failover where possible — manual DR procedures fail under pressure +- Test DR procedures quarterly with actual failover, not just documentation review +- Ensure DR site is geographically separated from primary site + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/dpia/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/dpia/SKILL.md new file mode 100644 index 0000000..22cf051 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/dpia/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data protection impact assessment with structured process, quality checks, and system integration +--- + +# Data Protection Impact Assessment + +## Purpose + +Create a comprehensive data protection impact assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data protection impact assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GDPR Article 35, ICO DPIA Guidance, CNIL DPIA Methodology + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data protection impact assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Processing Activities Assessed, Privacy Risks Identified, Mitigation Measures Implemented, DPO Consultation Status +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data protection impact assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Conduct DPIAs BEFORE processing begins — not retroactively + +## Output Format + +```markdown +# Data Protection Impact Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GDPR Article 35 +- ICO DPIA Guidance +- CNIL DPIA Methodology +- NIST Privacy Framework +- ISO/IEC 29134 + +## Key Metrics +- Processing Activities Assessed +- Privacy Risks Identified +- Mitigation Measures Implemented +- DPO Consultation Status +- Supervisory Authority Referral Need +- Data Subject Impact Score + +## Best Practices +- Conduct DPIAs BEFORE processing begins — not retroactively +- Assess necessity and proportionality of processing against the stated purpose +- Include data subject consultation where practicable +- Document the DPO advice and whether it was followed +- Reassess when processing purpose, scope, or context changes significantly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/encryption-standard/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/encryption-standard/SKILL.md new file mode 100644 index 0000000..4d43e8f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/encryption-standard/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a encryption & key management standard with structured process, quality checks, and system integration +--- + +# Encryption & Key Management Standard + +## Purpose + +Create a comprehensive encryption & key management standard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing encryption & key management standard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-57, NIST SP 800-175B, FIPS 140-3 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the encryption & key management standard +- Identify gaps, opportunities, and risks +- Define success metrics: Algorithm Compliance Rate, Key Rotation Frequency, Certificate Inventory Completeness, TLS Configuration Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the encryption & key management standard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Mandate AES-256 for data at rest and TLS 1.3 for data in transit as minimums + +## Output Format + +```markdown +# Encryption & Key Management Standard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-57 (Key Management) +- NIST SP 800-175B (Cryptographic Standards) +- FIPS 140-3 +- PCI DSS Req. 3-4 +- ENISA Crypto Recommendations + +## Key Metrics +- Algorithm Compliance Rate +- Key Rotation Frequency +- Certificate Inventory Completeness +- TLS Configuration Score +- Crypto Agility Readiness +- Deprecated Algorithm Usage Count + +## Best Practices +- Mandate AES-256 for data at rest and TLS 1.3 for data in transit as minimums +- Rotate encryption keys annually and immediately after suspected compromise +- Maintain a complete certificate inventory with automated expiry monitoring +- Plan for post-quantum cryptography migration (NIST PQC standards) +- Disable deprecated algorithms (DES, 3DES, RC4, MD5, SHA-1) with no exceptions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/forensics-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/forensics-report/SKILL.md new file mode 100644 index 0000000..323e683 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/forensics-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a digital forensics report with structured process, quality checks, and system integration +--- + +# Digital Forensics Report + +## Purpose + +Create a comprehensive digital forensics report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing digital forensics report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-86, ISO 27037, ACPO Good Practice Guide + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the digital forensics report +- Identify gaps, opportunities, and risks +- Define success metrics: Evidence Items Analyzed, Chain of Custody Integrity, Timeline Event Count, IOCs Discovered +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the digital forensics report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Maintain unbroken chain of custody with signed evidence logs + +## Output Format + +```markdown +# Digital Forensics Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-86 +- ISO 27037 +- ACPO Good Practice Guide +- EnCase/FTK Forensic Methodology +- Chain of Custody Standards + +## Key Metrics +- Evidence Items Analyzed +- Chain of Custody Integrity +- Timeline Event Count +- IOCs Discovered +- Forensic Image Verification (Hash Match) +- Tool Version Documentation + +## Best Practices +- Maintain unbroken chain of custody with signed evidence logs +- Create forensic images with verified hash values (SHA-256) before analysis +- Use write-blockers for all physical evidence acquisition +- Document every tool used, version, and command executed for reproducibility +- Present findings as factual observations — separate facts from analyst interpretation + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/hipaa-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/hipaa-assessment/SKILL.md new file mode 100644 index 0000000..98481ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/hipaa-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a hipaa security assessment with structured process, quality checks, and system integration +--- + +# HIPAA Security Assessment + +## Purpose + +Create a comprehensive hipaa security assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hipaa security assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Security Rule (45 CFR Part 164), HITECH Act, NIST SP 800-66 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hipaa security assessment +- Identify gaps, opportunities, and risks +- Define success metrics: ePHI Safeguard Coverage, Risk Assessment Completeness, BAA Inventory Compliance, Security Incident Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hipaa security assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Conduct a thorough ePHI inventory — you cannot protect what you do not know exists + +## Output Format + +```markdown +# HIPAA Security Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Security Rule (45 CFR Part 164) +- HIPAA Privacy Rule +- HITECH Act +- NIST SP 800-66 (HIPAA Implementation Guide) +- HHS OCR Audit Protocol + +## Key Metrics +- ePHI Safeguard Coverage (Administrative/Physical/Technical) +- Risk Assessment Completeness +- BAA Inventory Compliance +- Security Incident Count +- Training Completion Rate +- Audit Log Retention Compliance + +## Best Practices +- Conduct a thorough ePHI inventory — you cannot protect what you do not know exists +- Ensure all business associates have current BAAs (Business Associate Agreements) +- Implement minimum necessary standard for all ePHI access +- Maintain audit logs for all ePHI access with 6-year retention +- Train all workforce members (not just employees) who handle ePHI + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/iam-review/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/iam-review/SKILL.md new file mode 100644 index 0000000..24c1db1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/iam-review/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a iam access review report with structured process, quality checks, and system integration +--- + +# IAM Access Review Report + +## Purpose + +Create a comprehensive iam access review report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing iam access review report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-63, ISO 27001 (A.5.15-18), CIS Controls v8.1 (Controls 5, 6) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the iam access review report +- Identify gaps, opportunities, and risks +- Define success metrics: Orphaned Account Count, Excessive Permission Count, Segregation of Duties Violations, Access Review Completion Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the iam access review report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Review all privileged access quarterly and standard access semi-annually + +## Output Format + +```markdown +# IAM Access Review Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-63 (Digital Identity) +- ISO 27001 (A.5.15-18) +- CIS Controls v8.1 (Controls 5, 6) +- SOX Section 404 +- PCI DSS Req. 7-8 + +## Key Metrics +- Orphaned Account Count +- Excessive Permission Count +- Segregation of Duties Violations +- Access Review Completion Rate +- Mean Time to Revoke Terminated User Access +- Exception Count and Age + +## Best Practices +- Review all privileged access quarterly and standard access semi-annually +- Revoke terminated employee access within 24 hours — automate via HR integration +- Identify and remediate orphaned accounts (active accounts with no owner) +- Validate segregation of duties — no single person should approve and execute +- Document every access exception with risk acceptance and expiration date + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/incident-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/incident-report/SKILL.md new file mode 100644 index 0000000..bc41edc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/incident-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a incident report (post-incident) with structured process, quality checks, and system integration +--- + +# Incident Report (Post-Incident) + +## Purpose + +Create a comprehensive incident report (post-incident) that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident report (post-incident) documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-61, ISO 27035-2, VERIS + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident report (post-incident) +- Identify gaps, opportunities, and risks +- Define success metrics: Timeline Accuracy, Root Cause Identified (Yes/No), Impact Quantification ($), Lessons Learned Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident report (post-incident) using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the complete timeline from first indicator to full recovery + +## Output Format + +```markdown +# Incident Report (Post-Incident) + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-61 +- ISO 27035-2 +- VERIS +- FIRST TLP +- MITRE ATT&CK + +## Key Metrics +- Timeline Accuracy +- Root Cause Identified (Yes/No) +- Impact Quantification ($) +- Lessons Learned Count +- Remediation Implementation Rate +- Time to Full Recovery + +## Best Practices +- Document the complete timeline from first indicator to full recovery +- Identify root cause — not just proximate cause — using 5 Whys or Fishbone analysis +- Quantify business impact in dollars, downtime hours, and affected records +- Include specific, implementable lessons learned with assigned owners +- Mark the report with appropriate TLP classification for sharing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/incident-response-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/incident-response-plan/SKILL.md new file mode 100644 index 0000000..c6cc10a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/incident-response-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a incident response plan with structured process, quality checks, and system integration +--- + +# Incident Response Plan + +## Purpose + +Create a comprehensive incident response plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident response plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-61 Rev 2, SANS Incident Handling Process, ISO 27035 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident response plan +- Identify gaps, opportunities, and risks +- Define success metrics: Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), Incident Classification Accuracy, Communication Time to Stakeholders +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident response plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define incident classification levels (P1-P4) with clear escalation criteria + +## Output Format + +```markdown +# Incident Response Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-61 Rev 2 +- SANS Incident Handling Process +- ISO 27035 +- CISA Incident Response Playbooks +- FIRST CSIRT Framework + +## Key Metrics +- Mean Time to Detect (MTTD) +- Mean Time to Respond (MTTR) +- Incident Classification Accuracy +- Communication Time to Stakeholders +- Plan Test Frequency +- Evidence Preservation Rate + +## Best Practices +- Define incident classification levels (P1-P4) with clear escalation criteria +- Include communication templates for internal, customer, regulatory, and media notifications +- Test the plan via tabletop exercises at least twice per year +- Establish clear roles: Incident Commander, Technical Lead, Communications Lead, Legal +- Include evidence preservation procedures from the start — not as an afterthought + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/ir-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/ir-playbook/SKILL.md new file mode 100644 index 0000000..7f43842 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/ir-playbook/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a incident response playbook with structured process, quality checks, and system integration +--- + +# Incident Response Playbook + +## Purpose + +Create a comprehensive incident response playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident response playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-61 Rev 2, MITRE ATT&CK (Defensive), SANS PICERL + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident response playbook +- Identify gaps, opportunities, and risks +- Define success metrics: MTTR per Scenario Type, Containment Time, Evidence Collection Completeness, Playbook Execution Success Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident response playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Create separate playbooks per scenario: ransomware, phishing, data breach, insider threat, DDoS + +## Output Format + +```markdown +# Incident Response Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-61 Rev 2 +- MITRE ATT&CK (Defensive) +- SANS PICERL +- D3FEND +- CISA IR Playbooks + +## Key Metrics +- MTTR per Scenario Type +- Containment Time +- Evidence Collection Completeness +- Playbook Execution Success Rate +- Lessons Learned Implementation Rate +- Recovery Time per Scenario + +## Best Practices +- Create separate playbooks per scenario: ransomware, phishing, data breach, insider threat, DDoS +- Include exact commands, tool references, and decision trees — not just narrative +- Define containment actions that preserve forensic evidence +- Include communication flow diagrams for each stakeholder group +- Review and update playbooks after every real incident and every exercise + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/iso27001-isms/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/iso27001-isms/SKILL.md new file mode 100644 index 0000000..1981aae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/iso27001-isms/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a iso 27001 isms documentation with structured process, quality checks, and system integration +--- + +# ISO 27001 ISMS Documentation + +## Purpose + +Create a comprehensive iso 27001 isms documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing iso 27001 isms documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO/IEC 27001:2022, ISO/IEC 27002:2022, ISO/IEC 27005 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the iso 27001 isms documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Annex A Control Implementation %, Statement of Applicability Completeness, Internal Audit Nonconformity Count, Risk Treatment Plan Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the iso 27001 isms documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Scope the ISMS carefully — too broad makes certification impractical + +## Output Format + +```markdown +# ISO 27001 ISMS Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO/IEC 27001:2022 +- ISO/IEC 27002:2022 +- ISO/IEC 27005 (Risk Management) +- ISO/IEC 27017 (Cloud) +- ISO/IEC 27701 (Privacy) + +## Key Metrics +- Annex A Control Implementation % +- Statement of Applicability Completeness +- Internal Audit Nonconformity Count +- Risk Treatment Plan Progress +- Corrective Action Closure Rate +- Management Review Frequency + +## Best Practices +- Scope the ISMS carefully — too broad makes certification impractical +- Create a Statement of Applicability (SoA) mapping all 93 Annex A controls +- Conduct management reviews at least quarterly, not just annually +- Integrate risk assessment with business risk processes +- Train all employees within ISMS scope, not just IT staff + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/network-security-design/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/network-security-design/SKILL.md new file mode 100644 index 0000000..5ff45f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/network-security-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a network security design with structured process, quality checks, and system integration +--- + +# Network Security Design + +## Purpose + +Create a comprehensive network security design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing network security design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Purdue Model, NIST SP 800-41, CIS Controls v8.1 (Controls 9, 12, 13) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the network security design +- Identify gaps, opportunities, and risks +- Define success metrics: Segmentation Zone Count, Firewall Rule Count and Complexity, IDS/IPS Coverage %, DMZ Architecture Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the network security design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Segment networks by function and sensitivity — flat networks are indefensible + +## Output Format + +```markdown +# Network Security Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Purdue Model (OT Networks) +- NIST SP 800-41 (Firewalls) +- CIS Controls v8.1 (Controls 9, 12, 13) +- Zero Trust Network Access (ZTNA) +- Software-Defined Perimeter (SDP) + +## Key Metrics +- Segmentation Zone Count +- Firewall Rule Count and Complexity +- IDS/IPS Coverage % +- DMZ Architecture Compliance +- Unauthorized Traffic Flow Count +- East-West Traffic Visibility % + +## Best Practices +- Segment networks by function and sensitivity — flat networks are indefensible +- Document all firewall rules with business justification and expiration date +- Deploy IDS/IPS at trust boundary intersections +- Implement egress filtering — not just ingress +- Review and clean firewall rules quarterly — rule bloat creates blind spots + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/nist-csf-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/nist-csf-assessment/SKILL.md new file mode 100644 index 0000000..fea15a8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/nist-csf-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a nist csf assessment with structured process, quality checks, and system integration +--- + +# NIST CSF Assessment + +## Purpose + +Create a comprehensive nist csf assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nist csf assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST CSF 2.0 (6 Functions), NIST SP 800-53 Rev 5, CIS Controls v8.1 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nist csf assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Maturity Tier per Function (1-4), Category Implementation Score, Gap Count per Function, Target Profile Achievement % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nist csf assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Assess all 6 functions (Govern, Identify, Protect, Detect, Respond, Recover) — do not skip Govern + +## Output Format + +```markdown +# NIST CSF Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST CSF 2.0 (6 Functions) +- NIST SP 800-53 Rev 5 +- CIS Controls v8.1 (cross-mapping) +- NIST SP 800-37 (RMF) +- CMMC 2.0 + +## Key Metrics +- Maturity Tier per Function (1-4) +- Category Implementation Score +- Gap Count per Function +- Target Profile Achievement % +- Organizational Profile Completeness +- Cross-Framework Alignment Score + +## Best Practices +- Assess all 6 functions (Govern, Identify, Protect, Detect, Respond, Recover) — do not skip Govern +- Create both Current Profile and Target Profile for gap analysis +- Map implementation tiers (Partial to Adaptive) for each category +- Cross-reference with CIS Controls for actionable implementation guidance +- Engage business stakeholders — CSF is a business risk framework, not just IT + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/pam-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/pam-policy/SKILL.md new file mode 100644 index 0000000..074b089 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/pam-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a privileged access management policy with structured process, quality checks, and system integration +--- + +# Privileged Access Management Policy + +## Purpose + +Create a comprehensive privileged access management policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing privileged access management policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-53 (AC-6), CIS Controls v8.1 (Controls 5, 6), ISO 27001 (A.8.2-3) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the privileged access management policy +- Identify gaps, opportunities, and risks +- Define success metrics: Privileged Account Inventory Completeness, JIT Access Adoption Rate, Session Recording Coverage, Credential Rotation Frequency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the privileged access management policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Implement Just-in-Time (JIT) access — eliminate standing privileges + +## Output Format + +```markdown +# Privileged Access Management Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-53 (AC-6) +- CIS Controls v8.1 (Controls 5, 6) +- ISO 27001 (A.8.2-3) +- MITRE ATT&CK (Privilege Escalation) +- Gartner PAM Market Guide + +## Key Metrics +- Privileged Account Inventory Completeness +- JIT Access Adoption Rate +- Session Recording Coverage +- Credential Rotation Frequency +- Privilege Escalation Incident Count +- Break-Glass Usage Frequency + +## Best Practices +- Implement Just-in-Time (JIT) access — eliminate standing privileges where possible +- Record all privileged sessions for audit trail and forensic purposes +- Rotate privileged credentials automatically every 30-90 days +- Require MFA for all privileged access — no exceptions +- Maintain break-glass procedures for emergency access with post-use review + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/pci-dss-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/pci-dss-assessment/SKILL.md new file mode 100644 index 0000000..080dee1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/pci-dss-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a pci dss assessment with structured process, quality checks, and system integration +--- + +# PCI DSS Assessment + +## Purpose + +Create a comprehensive pci dss assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pci dss assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: PCI DSS 4.0, PCI SSC SAQ Types, PA-DSS + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pci dss assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Requirement Compliance Rate (12 Requirements), SAQ/ROC Completion Status, ASV Scan Pass Rate, Segmentation Validation Results +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pci dss assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Determine correct SAQ type based on actual cardholder data flow — not assumptions + +## Output Format + +```markdown +# PCI DSS Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- PCI DSS 4.0 +- PCI SSC SAQ Types (A, A-EP, B, C, D) +- PA-DSS +- PCI PIN Security +- PCI P2PE + +## Key Metrics +- Requirement Compliance Rate (12 Requirements) +- SAQ/ROC Completion Status +- ASV Scan Pass Rate +- Segmentation Validation Results +- Compensating Control Count +- CDE Scope Size + +## Best Practices +- Determine correct SAQ type based on actual cardholder data flow — not assumptions +- Minimize cardholder data environment (CDE) scope through segmentation and tokenization +- Run ASV scans quarterly and after any significant infrastructure change +- Document all compensating controls with detailed justification +- Track PCI DSS 4.0 future-dated requirements and verify compliance + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/pentest-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/pentest-report/SKILL.md new file mode 100644 index 0000000..906444c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/pentest-report/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a penetration test report with structured process, quality checks, and system integration +--- + +# Penetration Test Report + +## Purpose + +Create a comprehensive penetration test report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing penetration test report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP Testing Guide, PTES, NIST SP 800-115 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the penetration test report +- Identify gaps, opportunities, and risks +- Define success metrics: Vulnerability Count by Severity, CVSS Score Distribution, Remediation Rate, Retest Pass Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the penetration test report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Classify all findings using CVSS v4.0 with attack complexity context + +## Output Format + +```markdown +# Penetration Test Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP Testing Guide +- PTES (Penetration Testing Execution Standard) +- NIST SP 800-115 +- CVSS v4.0 +- MITRE ATT&CK +- CIS Controls v8.1 +- PCI DSS 11.3 + +## Key Metrics +- Vulnerability Count by Severity (Critical/High/Medium/Low) +- CVSS Score Distribution +- Remediation Rate +- Retest Pass Rate +- Mean Time to Remediate +- Finding Density per Application/Host +- Exploitability Score + +## Best Practices +- Classify all findings using CVSS v4.0 with attack complexity context +- Include proof-of-concept for every Critical and High finding +- Write executive summary for non-technical audience — max 2 pages +- Provide remediation steps with specific configuration changes, not generic advice +- Retest all Critical/High findings within 30 days + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/phishing-simulation-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/phishing-simulation-report/SKILL.md new file mode 100644 index 0000000..b52a137 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/phishing-simulation-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a phishing simulation campaign report with structured process, quality checks, and system integration +--- + +# Phishing Simulation Campaign Report + +## Purpose + +Create a comprehensive phishing simulation campaign report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing phishing simulation campaign report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SANS Security Awareness Maturity Model, NIST SP 800-50, Gartner Security Awareness Benchmarks + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the phishing simulation campaign report +- Identify gaps, opportunities, and risks +- Define success metrics: Email Open Rate, Link Click Rate, Credential Submission Rate, Report Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the phishing simulation campaign report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Use realistic, current phishing lure types (not obviously fake templates) + +## Output Format + +```markdown +# Phishing Simulation Campaign Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SANS Security Awareness Maturity Model +- NIST SP 800-50 +- Gartner Security Awareness Benchmarks +- KnowBe4/Proofpoint Simulation Frameworks +- Social Engineering Kill Chain + +## Key Metrics +- Email Open Rate +- Link Click Rate +- Credential Submission Rate +- Report Rate (employees who reported the phish) +- Department-Level Performance +- Trend vs. Previous Campaigns + +## Best Practices +- Use realistic, current phishing lure types (not obviously fake templates) +- Measure report rate alongside click rate — reporting culture is the goal +- Break down results by department, seniority level, and location +- Provide immediate teachable moments when users click — not delayed notifications +- Track trends across campaigns — single campaign results are noise, trends are signal + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/privacy-program-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/privacy-program-plan/SKILL.md new file mode 100644 index 0000000..5a5465c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/privacy-program-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a privacy program plan with structured process, quality checks, and system integration +--- + +# Privacy Program Plan + +## Purpose + +Create a comprehensive privacy program plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing privacy program plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST Privacy Framework, ISO/IEC 27701, GDPR Accountability Principle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the privacy program plan +- Identify gaps, opportunities, and risks +- Define success metrics: Regulatory Coverage %, DSAR Response Time, Consent Collection Rate, Privacy Training Completion Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the privacy program plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Map all applicable privacy regulations by jurisdiction and data type + +## Output Format + +```markdown +# Privacy Program Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST Privacy Framework +- ISO/IEC 27701 +- GDPR Accountability Principle +- APEC Cross-Border Privacy Rules +- IAPP Privacy Program Management + +## Key Metrics +- Regulatory Coverage (% of applicable laws mapped) +- DSAR Response Time (vs. SLA) +- Consent Collection Rate +- Privacy Training Completion Rate +- Privacy Impact Assessment Completion Rate +- Data Processing Inventory Completeness + +## Best Practices +- Map all applicable privacy regulations by jurisdiction and data type +- Implement Privacy by Design across all new projects and systems +- Automate DSAR workflows — manual processes do not scale +- Maintain a data processing inventory with legal basis for each activity +- Appoint a DPO with direct access to executive leadership + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/purple-team-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/purple-team-report/SKILL.md new file mode 100644 index 0000000..e884c14 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/purple-team-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a purple team assessment with structured process, quality checks, and system integration +--- + +# Purple Team Assessment + +## Purpose + +Create a comprehensive purple team assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing purple team assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MITRE ATT&CK, Purple Team Exercise Framework, SOC-CMM + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the purple team assessment +- Identify gaps, opportunities, and risks +- Define success metrics: ATT&CK Technique Coverage (%), Detection Rate per Technique, Mean Time to Detect per TTP, SIEM Rule Effectiveness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the purple team assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test specific ATT&CK techniques — not generic "attacks" + +## Output Format + +```markdown +# Purple Team Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MITRE ATT&CK +- Purple Team Exercise Framework +- SOC-CMM +- D3FEND +- Sigma Rules Standard +- NIST CSF 2.0 (Detect Function) + +## Key Metrics +- ATT&CK Technique Coverage (%) +- Detection Rate per Technique +- Mean Time to Detect per TTP +- SIEM Rule Effectiveness +- False Positive Rate Improvement +- Detection Gap Count +- Rule Tuning Actions Completed + +## Best Practices +- Test specific ATT&CK techniques — not generic "attacks" +- Document detection status per technique (Detected/Partially Detected/Missed/Not Tested) +- Create or tune SIEM rules in real-time during the exercise +- Measure before/after detection rates to quantify improvement +- Produce a detection coverage heat map against ATT&CK matrix + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/red-team-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/red-team-report/SKILL.md new file mode 100644 index 0000000..6e34848 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/red-team-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a red team engagement report with structured process, quality checks, and system integration +--- + +# Red Team Engagement Report + +## Purpose + +Create a comprehensive red team engagement report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing red team engagement report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MITRE ATT&CK, Cyber Kill Chain, TIBER-EU + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the red team engagement report +- Identify gaps, opportunities, and risks +- Define success metrics: Objectives Achieved (%), MTTD by Blue Team, Attack Paths Discovered, Detection Coverage (%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the red team engagement report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Map every action to MITRE ATT&CK tactics and techniques + +## Output Format + +```markdown +# Red Team Engagement Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MITRE ATT&CK +- Cyber Kill Chain +- TIBER-EU +- CBEST +- PTES +- Red Team Operations Framework + +## Key Metrics +- Objectives Achieved (%) +- MTTD by Blue Team +- Attack Paths Discovered +- Detection Coverage (% of TTPs detected) +- Dwell Time +- Lateral Movement Steps +- Data Exfiltration Success Rate + +## Best Practices +- Map every action to MITRE ATT&CK tactics and techniques +- Document the full attack narrative chronologically — not just findings +- Measure blue team detection performance explicitly with timestamps +- Include "what could have happened" impact analysis for stopped attack paths +- Debrief with blue team within 48 hours of engagement completion + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/risk-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/risk-assessment/SKILL.md new file mode 100644 index 0000000..acc0ede --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/risk-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cybersecurity risk assessment with structured process, quality checks, and system integration +--- + +# Cybersecurity Risk Assessment + +## Purpose + +Create a comprehensive cybersecurity risk assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cybersecurity risk assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-30, ISO 27005, FAIR + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cybersecurity risk assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Total Risks Identified, Risk Distribution by Level, Residual Risk Count, Risk Treatment Coverage % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cybersecurity risk assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Quantify risks in financial terms using FAIR + +## Output Format + +```markdown +# Cybersecurity Risk Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-30 +- ISO 27005 +- FAIR (Factor Analysis of Information Risk) +- OCTAVE +- CIS RAM + +## Key Metrics +- Total Risks Identified +- Risk Distribution by Level +- Residual Risk Count +- Risk Treatment Coverage % +- Cost of Risk Mitigation vs. Exposure +- Risk Score Trend + +## Best Practices +- Quantify risks in financial terms using FAIR — qualitative-only assessments lack decision power +- Include threat likelihood AND business impact in every risk score +- Separate inherent risk from residual risk (after controls) +- Involve business stakeholders — they understand impact better than IT +- Update risk assessments after every significant change, not just annually + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/risk-register/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/risk-register/SKILL.md new file mode 100644 index 0000000..dd80b5b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/risk-register/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a risk register with structured process, quality checks, and system integration +--- + +# Risk Register + +## Purpose + +Create a comprehensive risk register that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing risk register documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO 31000, ISO 27005, NIST SP 800-39 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the risk register +- Identify gaps, opportunities, and risks +- Define success metrics: Total Open Risks, Risk Age (Days Open), Risk Treatment Status Distribution, Top 10 Risks by Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the risk register using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Assign a named owner for every risk — unowned risks never get mitigated + +## Output Format + +```markdown +# Risk Register + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO 31000 +- ISO 27005 +- NIST SP 800-39 +- FAIR +- COSO ERM Framework + +## Key Metrics +- Total Open Risks +- Risk Age (Days Open) +- Risk Treatment Status Distribution +- Top 10 Risks by Score +- Risk Trend (New vs. Closed per Quarter) +- Overdue Treatment Actions + +## Best Practices +- Assign a named owner for every risk — unowned risks never get mitigated +- Review the register quarterly with risk owners present +- Track risk treatment decisions explicitly: Accept, Mitigate, Transfer, Avoid +- Include residual risk scores after controls — not just inherent risk +- Integrate with the enterprise risk management process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/runbook/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/runbook/SKILL.md new file mode 100644 index 0000000..85ad147 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/runbook/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a operational runbook with structured process, quality checks, and system integration +--- + +# Operational Runbook + +## Purpose + +Create a comprehensive operational runbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing operational runbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ITIL v4, SRE Practices (Google), NIST SP 800-137 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the operational runbook +- Identify gaps, opportunities, and risks +- Define success metrics: Runbook Execution Time, Error Rate During Execution, Automation Coverage %, Knowledge Transfer Success Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the operational runbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write runbooks as numbered steps with exact commands — assume the reader is unfamiliar + +## Output Format + +```markdown +# Operational Runbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ITIL v4 (Operational Management) +- SRE Practices (Google) +- NIST SP 800-137 (Continuous Monitoring) +- ISO 20000 +- DevOps Automation Principles + +## Key Metrics +- Runbook Execution Time +- Error Rate During Execution +- Automation Coverage % +- Knowledge Transfer Success Rate +- Runbook Currency (Last Updated) +- Step Completion Rate + +## Best Practices +- Write runbooks as numbered steps with exact commands — assume the reader is unfamiliar +- Include prerequisite checks, expected outputs, and troubleshooting for each step +- Add rollback procedures for every change-making operation +- Mark manual steps as automation candidates with effort estimates +- Review and test runbooks quarterly — outdated runbooks cause more harm than no runbook + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/sbom/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/sbom/SKILL.md new file mode 100644 index 0000000..e02bb69 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/sbom/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a software bill of materials (sbom) with structured process, quality checks, and system integration +--- + +# Software Bill of Materials (SBOM) + +## Purpose + +Create a comprehensive software bill of materials (sbom) that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing software bill of materials (sbom) documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NTIA Minimum Elements, CISA SBOM Guidance, CycloneDX + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the software bill of materials (sbom) +- Identify gaps, opportunities, and risks +- Define success metrics: Component Count, Known Vulnerability Count (CVEs), License Compliance Rate, SBOM Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the software bill of materials (sbom) using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Generate SBOMs automatically in CI/CD pipeline — manual inventory is always incomplete + +## Output Format + +```markdown +# Software Bill of Materials (SBOM) + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NTIA Minimum Elements +- CISA SBOM Guidance (2025) +- CycloneDX +- SPDX (ISO/IEC 5962) +- SLSA Framework + +## Key Metrics +- Component Count +- Known Vulnerability Count (CVEs) +- License Compliance Rate +- SBOM Freshness (Last Generated) +- Dependency Depth +- Transitive Dependency Count + +## Best Practices +- Generate SBOMs automatically in CI/CD pipeline — manual inventory is always incomplete +- Use CycloneDX or SPDX format for interoperability +- Include transitive dependencies — most vulnerabilities are in indirect dependencies +- Cross-reference all components against NVD/OSV for known CVEs +- Update SBOMs with every build, not just releases + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/sdlc-security-gates/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/sdlc-security-gates/SKILL.md new file mode 100644 index 0000000..ac5d103 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/sdlc-security-gates/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a secure sdlc security gates with structured process, quality checks, and system integration +--- + +# Secure SDLC Security Gates + +## Purpose + +Create a comprehensive secure sdlc security gates that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing secure sdlc security gates documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Microsoft SDL, OWASP SAMM, NIST SSDF (SP 800-218) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the secure sdlc security gates +- Identify gaps, opportunities, and risks +- Define success metrics: Gate Pass Rate per Phase, Critical Finding Escape Rate, Security Requirement Coverage, Mean Time to Fix Security Bugs +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the secure sdlc security gates using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define mandatory gates at design, code, build, test, and deploy phases + +## Output Format + +```markdown +# Secure SDLC Security Gates + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Microsoft SDL +- OWASP SAMM +- NIST SSDF (SP 800-218) +- BSIMM +- DevSecOps Maturity Model (DSOMM) + +## Key Metrics +- Gate Pass Rate per Phase +- Critical Finding Escape Rate +- Security Requirement Coverage +- Mean Time to Fix Security Bugs +- Security Training Completion Rate +- Automated Scan Coverage + +## Best Practices +- Define mandatory gates at design, code, build, test, and deploy phases +- Automate SAST, DAST, SCA, and secrets scanning in CI/CD pipeline +- Block deployments with Critical/High findings — no exceptions without CISO sign-off +- Require threat models for all new features above a risk threshold +- Track security bug fix time separately from functional bugs — they have different SLAs + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/secure-code-review/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/secure-code-review/SKILL.md new file mode 100644 index 0000000..479dfb3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/secure-code-review/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a secure code review report with structured process, quality checks, and system integration +--- + +# Secure Code Review Report + +## Purpose + +Create a comprehensive secure code review report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing secure code review report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP Code Review Guide, OWASP ASVS v4.0, CWE Top 25 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the secure code review report +- Identify gaps, opportunities, and risks +- Define success metrics: Vulnerability Count by CWE Category, Severity Distribution, Lines of Code Reviewed, Finding Density +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the secure code review report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Combine SAST tool results with manual review — neither alone is sufficient + +## Output Format + +```markdown +# Secure Code Review Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP Code Review Guide +- OWASP ASVS v4.0 +- CWE Top 25 +- SANS Top 25 +- NIST SSDF (SP 800-218) + +## Key Metrics +- Vulnerability Count by CWE Category +- Severity Distribution (Critical/High/Medium/Low) +- Lines of Code Reviewed +- Finding Density (Findings per KLOC) +- Remediation Acceptance Rate +- Review Turnaround Time + +## Best Practices +- Combine SAST tool results with manual review — neither alone is sufficient +- Focus manual review on authentication, authorization, cryptography, and input validation +- Classify findings using CWE identifiers for consistency and trending +- Provide remediation code examples, not just vulnerability descriptions +- Review within the development sprint — findings delivered after release have 10x lower fix rate + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/secure-design-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/secure-design-spec/SKILL.md new file mode 100644 index 0000000..09e029d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/secure-design-spec/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a secure design specification with structured process, quality checks, and system integration +--- + +# Secure Design Specification + +## Purpose + +Create a comprehensive secure design specification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing secure design specification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP Secure Design Principles, Microsoft SDL, NIST SSDF (SP 800-218) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the secure design specification +- Identify gaps, opportunities, and risks +- Define success metrics: Security Requirements Coverage, Threat Mitigation Coverage, Design Review Findings, Crypto Standard Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the secure design specification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define security requirements before functional requirements + +## Output Format + +```markdown +# Secure Design Specification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP Secure Design Principles +- Microsoft SDL +- NIST SSDF (SP 800-218) +- BSIMM +- Security by Design (ENISA) + +## Key Metrics +- Security Requirements Coverage +- Threat Mitigation Coverage +- Design Review Findings +- Crypto Standard Compliance +- Authentication Mechanism Strength +- Data Protection Control Count + +## Best Practices +- Define security requirements before functional requirements +- Specify authentication, authorization, and encryption at the design phase +- Apply least privilege and defense in depth as architectural constraints +- Document all trust assumptions explicitly — they become attack vectors when wrong +- Include data flow diagrams with classification labels for every data store + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/security-architecture-review/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/security-architecture-review/SKILL.md new file mode 100644 index 0000000..7bb18de --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/security-architecture-review/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a security architecture review with structured process, quality checks, and system integration +--- + +# Security Architecture Review + +## Purpose + +Create a comprehensive security architecture review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing security architecture review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: TOGAF Security Architecture, SABSA, NIST SP 800-160 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the security architecture review +- Identify gaps, opportunities, and risks +- Define success metrics: Control Coverage %, Architecture Gap Count, Defense-in-Depth Layer Score, Compliance Alignment % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the security architecture review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Review architecture diagrams with explicit security control annotations + +## Output Format + +```markdown +# Security Architecture Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- TOGAF Security Architecture +- SABSA +- NIST SP 800-160 +- Zero Trust Architecture (NIST SP 800-207) +- Defense in Depth Model +- ISO 27001 Annex A + +## Key Metrics +- Control Coverage % +- Architecture Gap Count +- Defense-in-Depth Layer Score +- Compliance Alignment % +- Risk Reduction Estimate +- Single Points of Failure Count + +## Best Practices +- Review architecture diagrams with explicit security control annotations +- Validate defense-in-depth — ensure no single-layer protection for critical assets +- Map each architectural component to specific security controls +- Identify single points of failure in security infrastructure +- Assess both north-south and east-west traffic security controls + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/security-awareness-program/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/security-awareness-program/SKILL.md new file mode 100644 index 0000000..de60498 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/security-awareness-program/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a security awareness training program with structured process, quality checks, and system integration +--- + +# Security Awareness Training Program + +## Purpose + +Create a comprehensive security awareness training program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing security awareness training program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-50, SANS Security Awareness Maturity Model, ISO 27001 (A.6.3) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the security awareness training program +- Identify gaps, opportunities, and risks +- Define success metrics: Training Completion Rate, Phishing Click Rate, Security Incident Report Rate, Knowledge Assessment Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the security awareness training program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Deliver training in short modules (5-10 min) monthly — not annual marathons + +## Output Format + +```markdown +# Security Awareness Training Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-50 +- SANS Security Awareness Maturity Model +- ISO 27001 (A.6.3) +- CIS Controls v8.1 (Control 14) +- Kirkpatrick Training Evaluation Model + +## Key Metrics +- Training Completion Rate +- Phishing Simulation Click Rate +- Security Incident Report Rate +- Knowledge Assessment Score +- Behavior Change Measurement +- Role-Based Training Coverage + +## Best Practices +- Deliver training in short modules (5-10 min) monthly — not annual marathon sessions +- Use role-based training: developers get secure coding, executives get BEC/whaling +- Measure behavior change, not just completion rates +- Run phishing simulations 3-4 times per year with progressive difficulty +- Gamify the program — leaderboards and positive reinforcement outperform punishment + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/security-monitoring-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/security-monitoring-plan/SKILL.md new file mode 100644 index 0000000..3c0fa62 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/security-monitoring-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a security monitoring plan with structured process, quality checks, and system integration +--- + +# Security Monitoring Plan + +## Purpose + +Create a comprehensive security monitoring plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing security monitoring plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-137, SOC-CMM, MITRE ATT&CK Data Sources + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the security monitoring plan +- Identify gaps, opportunities, and risks +- Define success metrics: Log Source Coverage %, Alert Rule Count by Category, MTTD per Alert Type, Log Retention Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the security monitoring plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Inventory all log sources and map to MITRE ATT&CK data source requirements + +## Output Format + +```markdown +# Security Monitoring Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-137 +- SOC-CMM +- MITRE ATT&CK Data Sources +- CIS Controls v8.1 (Control 8) +- ISO 27001 (A.8.15-16) + +## Key Metrics +- Log Source Coverage % +- Alert Rule Count by Category +- MTTD per Alert Type +- Log Retention Compliance +- Monitoring Gap Count +- SIEM Ingestion Health + +## Best Practices +- Inventory all log sources and map to MITRE ATT&CK data source requirements +- Define retention periods per log type based on compliance and investigation needs +- Monitor the monitoring — alert on SIEM ingestion failures and agent disconnects +- Prioritize detection use cases by threat likelihood and business impact +- Include capacity planning — log volumes grow 20-30% annually + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/security-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/security-policy/SKILL.md new file mode 100644 index 0000000..0c7bc13 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/security-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a information security policy with structured process, quality checks, and system integration +--- + +# Information Security Policy + +## Purpose + +Create a comprehensive information security policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing information security policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: ISO 27001:2022 (Clause 5.2), NIST SP 800-12, SANS Policy Templates + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the information security policy +- Identify gaps, opportunities, and risks +- Define success metrics: Policy Coverage (% of required topics), Employee Acknowledgment Rate, Policy Exception Count, Policy Review Currency +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the information security policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Write policies in clear, non-technical language — they apply to all employees + +## Output Format + +```markdown +# Information Security Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- ISO 27001:2022 (Clause 5.2) +- NIST SP 800-12 +- SANS Policy Templates +- CIS Controls v8.1 +- COBIT 2019 + +## Key Metrics +- Policy Coverage (% of required topics) +- Employee Acknowledgment Rate +- Policy Exception Count +- Policy Review Currency +- Violation Incident Rate +- Policy Update Frequency + +## Best Practices +- Write policies in clear, non-technical language — they apply to all employees +- Include enforcement mechanisms and consequences for violations +- Review and update all policies annually with version control +- Maintain a policy exception process with documented risk acceptance +- Cover at minimum: acceptable use, access control, data handling, incident response, remote work, BYOD + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/soc-maturity-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/soc-maturity-assessment/SKILL.md new file mode 100644 index 0000000..f44af09 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/soc-maturity-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a soc maturity assessment with structured process, quality checks, and system integration +--- + +# SOC Maturity Assessment + +## Purpose + +Create a comprehensive soc maturity assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soc maturity assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SOC-CMM (5 Domains, 5 Levels), MITRE ATT&CK Coverage Matrix, Carnegie Mellon SOC Assessment + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soc maturity assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Overall Maturity Level (1-5), Domain Scores, ATT&CK Detection Coverage %, Analyst-to-Alert Ratio +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soc maturity assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Assess all 5 SOC-CMM domains — technology alone does not make a mature SOC + +## Output Format + +```markdown +# SOC Maturity Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SOC-CMM (5 Domains, 5 Levels) +- MITRE ATT&CK Coverage Matrix +- Carnegie Mellon SOC Assessment +- NIST CSF Detect Function +- CIS Controls v8.1 (Controls 8, 13) + +## Key Metrics +- Overall Maturity Level (1-5) +- Domain Scores (Business, People, Process, Technology, Services) +- ATT&CK Detection Coverage % +- Analyst-to-Alert Ratio +- Tool Utilization Rate +- Staff Retention Rate + +## Best Practices +- Assess all 5 SOC-CMM domains — technology alone does not make a mature SOC +- Measure detection coverage against MITRE ATT&CK matrix visually +- Benchmark analyst-to-alert ratio — over 50 alerts/analyst/day indicates tuning problems +- Include staffing, training, and retention in the assessment scope +- Create a 12-month improvement roadmap with quarterly milestones + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/soc-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/soc-playbook/SKILL.md new file mode 100644 index 0000000..30f3c45 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/soc-playbook/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a soc analyst playbook with structured process, quality checks, and system integration +--- + +# SOC Analyst Playbook + +## Purpose + +Create a comprehensive soc analyst playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soc analyst playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SOC-CMM, MITRE ATT&CK, NIST SP 800-61 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soc analyst playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Mean Time to Triage, Alert Closure Rate, Escalation Accuracy, False Positive Rate per Use Case +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soc analyst playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structure playbooks as decision trees — not narrative paragraphs + +## Output Format + +```markdown +# SOC Analyst Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SOC-CMM +- MITRE ATT&CK +- NIST SP 800-61 +- Sigma Detection Rules +- SOAR Workflow Design + +## Key Metrics +- Mean Time to Triage +- Alert Closure Rate +- Escalation Accuracy +- False Positive Rate per Use Case +- Analyst Consistency Score +- Playbook Coverage (% of alert types) + +## Best Practices +- Structure playbooks as decision trees — not narrative paragraphs +- Include exact log queries (SIEM syntax) for investigation steps +- Define clear escalation criteria with specific thresholds +- Document false positive indicators to reduce alert fatigue +- Update playbooks after every significant incident or detection gap discovery + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/soc2-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/soc2-report/SKILL.md new file mode 100644 index 0000000..1ca3eb9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/soc2-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a soc 2 compliance report with structured process, quality checks, and system integration +--- + +# SOC 2 Compliance Report + +## Purpose + +Create a comprehensive soc 2 compliance report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soc 2 compliance report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AICPA Trust Services Criteria, SOC 2 Type I/II, COSO Internal Control Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soc 2 compliance report +- Identify gaps, opportunities, and risks +- Define success metrics: Control Count by Trust Category, Exception Rate, Remediation Completion Rate, Evidence Collection Completeness % +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soc 2 compliance report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with Type I (point-in-time) to establish baseline before Type II (period) + +## Output Format + +```markdown +# SOC 2 Compliance Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AICPA Trust Services Criteria (TSC) +- SOC 2 Type I/II +- COSO Internal Control Framework +- CIS Controls v8.1 +- ISO 27001 (cross-mapping) + +## Key Metrics +- Control Count by Trust Category +- Exception Rate +- Remediation Completion Rate +- Audit Finding Trend +- Evidence Collection Completeness % +- Control Effectiveness Score + +## Best Practices +- Start with Type I (point-in-time) to establish baseline before Type II (period) +- Map existing controls to Trust Services Criteria before identifying gaps +- Automate evidence collection — manual evidence gathering does not scale +- Maintain continuous monitoring, not just annual audit preparation +- Cross-map SOC 2 controls to ISO 27001 for dual-framework efficiency + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/social-engineering-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/social-engineering-assessment/SKILL.md new file mode 100644 index 0000000..25f9ac1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/social-engineering-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social engineering assessment with structured process, quality checks, and system integration +--- + +# Social Engineering Assessment + +## Purpose + +Create a comprehensive social engineering assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social engineering assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-50, SANS Security Awareness Maturity Model, Social Engineering Penetration Testing Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social engineering assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Phishing Click Rate, Credential Submission Rate, Reporting Rate, Department-Level Susceptibility +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social engineering assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure reporting rate alongside click rate — a reporting culture matters more + +## Output Format + +```markdown +# Social Engineering Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-50 +- SANS Security Awareness Maturity Model +- Social Engineering Penetration Testing Framework +- Cialdini's Principles of Influence +- OSINT Framework +- MITRE ATT&CK (Initial Access) + +## Key Metrics +- Phishing Click Rate +- Credential Submission Rate +- Reporting Rate +- Department-Level Susceptibility +- Vishing Success Rate +- Physical Access Test Results +- Training Effectiveness Score + +## Best Practices +- Run phishing simulations with graduated difficulty (generic → targeted → spear phishing) +- Measure reporting rate alongside click rate — a reporting culture matters more +- Break down results by department and seniority for targeted training +- Include vishing (phone) and physical access tests, not just email phishing +- Never publicly shame individuals — focus on organizational improvement + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/tabletop-exercise/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/tabletop-exercise/SKILL.md new file mode 100644 index 0000000..66d9ce5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/tabletop-exercise/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a tabletop exercise & after-action report with structured process, quality checks, and system integration +--- + +# Tabletop Exercise & After-Action Report + +## Purpose + +Create a comprehensive tabletop exercise & after-action report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tabletop exercise & after-action report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CISA CTEPs, FEMA HSEEP, NIST SP 800-84 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tabletop exercise & after-action report +- Identify gaps, opportunities, and risks +- Define success metrics: Participant Engagement Score, Gap Count Identified, Decision Point Performance, Communication Effectiveness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tabletop exercise & after-action report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Design scenarios based on real-world threats relevant to the organization + +## Output Format + +```markdown +# Tabletop Exercise & After-Action Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CISA Tabletop Exercise Packages (CTEPs) +- FEMA HSEEP +- NIST SP 800-84 +- ISO 22398 +- MITRE ATT&CK Scenarios + +## Key Metrics +- Participant Engagement Score +- Gap Count Identified +- Decision Point Performance +- Communication Effectiveness +- Remediation Actions Generated +- Executive Participation Rate + +## Best Practices +- Design scenarios based on real-world threats relevant to the organization +- Include injects (surprise developments) to test decision-making under pressure +- Involve executive leadership — not just technical teams +- Produce an after-action report within 5 business days with assigned remediation owners +- Run at least 2 exercises per year covering different scenarios + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/threat-intel-report/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-intel-report/SKILL.md new file mode 100644 index 0000000..7cdbc37 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-intel-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a threat intelligence report with structured process, quality checks, and system integration +--- + +# Threat Intelligence Report + +## Purpose + +Create a comprehensive threat intelligence report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing threat intelligence report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MITRE ATT&CK, Diamond Model of Intrusion Analysis, Cyber Kill Chain + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the threat intelligence report +- Identify gaps, opportunities, and risks +- Define success metrics: IOCs Produced per Report, TTPs Mapped to ATT&CK, Intelligence Actionability Rate, Time from Event to Report +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the threat intelligence report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Tag all reports with TLP classification for appropriate sharing + +## Output Format + +```markdown +# Threat Intelligence Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MITRE ATT&CK +- Diamond Model of Intrusion Analysis +- Cyber Kill Chain +- Traffic Light Protocol (TLP) +- STIX/TAXII +- FIRST CSIRT Framework + +## Key Metrics +- IOCs Produced per Report +- TTPs Mapped to ATT&CK +- Intelligence Actionability Rate +- Time from Event to Report +- Consumer Feedback Score +- Confidence Level Distribution +- Threat Relevance Score + +## Best Practices +- Tag all reports with TLP classification for appropriate sharing +- Map threat actor TTPs to MITRE ATT&CK for defensive action mapping +- Include IOCs in machine-readable format (STIX 2.1) alongside narrative +- Assess confidence levels for all analytical judgments (High/Medium/Low) +- Focus on threats relevant to the organization's sector and technology stack + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/threat-landscape-briefing/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-landscape-briefing/SKILL.md new file mode 100644 index 0000000..4f66809 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-landscape-briefing/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a threat landscape briefing with structured process, quality checks, and system integration +--- + +# Threat Landscape Briefing + +## Purpose + +Create a comprehensive threat landscape briefing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing threat landscape briefing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: MITRE ATT&CK, ENISA Threat Landscape, Verizon DBIR + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the threat landscape briefing +- Identify gaps, opportunities, and risks +- Define success metrics: Active Threat Groups Targeting Sector, Top TTPs by Frequency, Ransomware Incident Rate, Zero-Day Exploitation Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the threat landscape briefing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Tailor briefings to the specific industry vertical and technology stack + +## Output Format + +```markdown +# Threat Landscape Briefing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- MITRE ATT&CK +- ENISA Threat Landscape +- Verizon DBIR +- CrowdStrike Global Threat Report +- Mandiant M-Trends +- CISA Advisories + +## Key Metrics +- Active Threat Groups Targeting Sector +- Top TTPs by Frequency +- Ransomware Incident Rate (Industry) +- Phishing Campaign Volume +- Zero-Day Exploitation Rate +- Supply Chain Attack Trend +- Geopolitical Risk Indicators + +## Best Practices +- Tailor briefings to the specific industry vertical and technology stack +- Reference current threat intelligence reports (DBIR, M-Trends, ENISA) for credibility +- Include "so what" recommendations — briefings without actions are just news +- Present trends over 6-12 months, not single-point snapshots +- Keep executive briefings to 10 minutes with visual threat heat maps + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/threat-model/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-model/SKILL.md new file mode 100644 index 0000000..61169aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/threat-model/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a threat model with structured process, quality checks, and system integration +--- + +# Threat Model + +## Purpose + +Create a comprehensive threat model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing threat model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: STRIDE, PASTA, LINDDUN + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the threat model +- Identify gaps, opportunities, and risks +- Define success metrics: Threats Identified per Component, Mitigations Coverage %, Residual Risk Score, Trust Boundary Violations +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the threat model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Create data flow diagrams with explicit trust boundaries before identifying threats + +## Output Format + +```markdown +# Threat Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- STRIDE +- PASTA (Process for Attack Simulation and Threat Analysis) +- DREAD +- LINDDUN (Privacy Threats) +- MITRE ATT&CK +- Attack Trees + +## Key Metrics +- Threats Identified per Component +- Mitigations Coverage % +- Residual Risk Score +- Trust Boundary Violations +- Threat-to-Mitigation Ratio +- Data Flow Diagram Completeness +- Abuse Case Coverage + +## Best Practices +- Create data flow diagrams with explicit trust boundaries before identifying threats +- Apply STRIDE per-element systematically — not ad hoc brainstorming +- Prioritize threats using DREAD or risk matrix (likelihood x impact) +- Update threat models when architecture changes — they are living documents +- Include abuse cases alongside use cases in the threat enumeration + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/vendor-risk-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/vendor-risk-assessment/SKILL.md new file mode 100644 index 0000000..169e926 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/vendor-risk-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a vendor/third-party risk assessment with structured process, quality checks, and system integration +--- + +# Vendor/Third-Party Risk Assessment + +## Purpose + +Create a comprehensive vendor/third-party risk assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor/third-party risk assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: SIG, CAIQ, NIST SP 800-161 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor/third-party risk assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Vendor Risk Rating, Questionnaire Completion Rate, SOC 2/ISO Certificate Status, Contractual Security Compliance +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor/third-party risk assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Tier vendors by data access and business criticality + +## Output Format + +```markdown +# Vendor/Third-Party Risk Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- SIG (Standardized Information Gathering) +- CAIQ (Consensus Assessments Initiative Questionnaire) +- NIST SP 800-161 +- ISO 27036 +- CIS Controls v8.1 (Control 15) + +## Key Metrics +- Vendor Risk Rating (Critical/High/Medium/Low) +- Questionnaire Completion Rate +- SOC 2/ISO 27001 Certificate Status +- Contractual Security Requirement Compliance +- Vendor Incident History +- Fourth-Party Risk Count + +## Best Practices +- Tier vendors by data access and business criticality — not all need the same assessment +- Require SOC 2 Type II or ISO 27001 from all vendors handling sensitive data +- Include right-to-audit clauses in contracts +- Monitor vendors continuously — point-in-time assessments miss emerging risks +- Assess fourth-party risk for critical dependencies + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/vuln-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/vuln-assessment/SKILL.md new file mode 100644 index 0000000..67844a1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/vuln-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a vulnerability assessment report with structured process, quality checks, and system integration +--- + +# Vulnerability Assessment Report + +## Purpose + +Create a comprehensive vulnerability assessment report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vulnerability assessment report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CVSS v4.0, CIS Controls v8.1, NIST SP 800-40 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vulnerability assessment report +- Identify gaps, opportunities, and risks +- Define success metrics: Total Vulnerabilities by Severity, Patch Compliance Rate, Vulnerability Density per Host, Mean Time to Remediate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vulnerability assessment report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Prioritize by exploitability (EPSS score), not just CVSS severity + +## Output Format + +```markdown +# Vulnerability Assessment Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CVSS v4.0 +- CIS Controls v8.1 +- NIST SP 800-40 (Patch Management) +- CVE/NVD Database +- CISA KEV (Known Exploited Vulnerabilities) +- EPSS (Exploit Prediction Scoring System) + +## Key Metrics +- Total Vulnerabilities by Severity +- Patch Compliance Rate +- Vulnerability Density per Host +- Mean Time to Remediate +- Age of Open Vulnerabilities +- EPSS Score Distribution +- CISA KEV Match Count + +## Best Practices +- Scan with both authenticated and unauthenticated methods for complete coverage +- Cross-reference findings against CISA KEV for active exploitation status +- Remove false positives through manual validation before reporting +- Track vulnerability trends over time — single snapshots are insufficient +- Prioritize by exploitability (EPSS score), not just CVSS severity + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/web-app-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/web-app-assessment/SKILL.md new file mode 100644 index 0000000..b194b68 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/web-app-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a web application security assessment with structured process, quality checks, and system integration +--- + +# Web Application Security Assessment + +## Purpose + +Create a comprehensive web application security assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing web application security assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: OWASP Top 10, OWASP ASVS v4.0, OWASP Testing Guide v4.2 + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the web application security assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Findings per OWASP Category, Critical/High Vulnerability Count, ASVS Compliance Level, Injection Flaw Count +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the web application security assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test against all OWASP Top 10 categories systematically + +## Output Format + +```markdown +# Web Application Security Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- OWASP Top 10 (2021) +- OWASP ASVS v4.0 +- OWASP Testing Guide v4.2 +- CWE Top 25 +- SANS Top 25 +- NIST SP 800-53 (SI Controls) + +## Key Metrics +- Findings per OWASP Category +- Critical/High Vulnerability Count +- ASVS Compliance Level +- Injection Flaw Count +- Authentication Bypass Count +- API Security Finding Count +- Remediation Acceptance Rate + +## Best Practices +- Test against all OWASP Top 10 categories systematically +- Verify both automated scanner findings and manual testing results +- Test authentication flows for bypass, session management flaws, and privilege escalation +- Check all API endpoints (REST, GraphQL) for authorization bypass +- Document all input validation failures with exact payloads used + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/wireless-security-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/wireless-security-assessment/SKILL.md new file mode 100644 index 0000000..478c6c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/wireless-security-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a wireless security assessment with structured process, quality checks, and system integration +--- + +# Wireless Security Assessment + +## Purpose + +Create a comprehensive wireless security assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wireless security assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: IEEE 802.11 Security Standards, WPA3/SAE Protocol, CIS Controls v8.1 (Control 12) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wireless security assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Rogue AP Count, WPA2/WPA3 Adoption Rate, Segmentation Violations, Evil Twin Detection Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wireless security assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Enumerate all SSIDs including hidden networks and rogue access points + +## Output Format + +```markdown +# Wireless Security Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- IEEE 802.11 Security Standards +- WPA3/SAE Protocol +- CIS Controls v8.1 (Control 12) +- PCI DSS Req. 11.1 +- NIST SP 800-153 +- Wi-Fi Alliance Security Certification + +## Key Metrics +- Rogue AP Count +- WPA2/WPA3 Adoption Rate +- Segmentation Violations +- Evil Twin Detection Rate +- Wireless IDS Alert Volume +- Encryption Protocol Distribution +- Client Isolation Compliance + +## Best Practices +- Enumerate all SSIDs including hidden networks and rogue access points +- Validate network segmentation between wireless and critical internal networks +- Test for WPA2 downgrade attacks where WPA3 is not enforced +- Conduct evil twin attack testing to assess client vulnerability +- Verify wireless IDS/WIPS is deployed and alerting correctly + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/cybersecurity/zero-trust-design/SKILL.md b/clowdex-download/.claude/.claude/skills/cybersecurity/zero-trust-design/SKILL.md new file mode 100644 index 0000000..119adde --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/cybersecurity/zero-trust-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a zero trust architecture design with structured process, quality checks, and system integration +--- + +# Zero Trust Architecture Design + +## Purpose + +Create a comprehensive zero trust architecture design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Cybersecurity & Information Security + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information (systems, scope, environment) + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing zero trust architecture design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: NIST SP 800-207, CISA Zero Trust Maturity Model, Google BeyondCorp + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the zero trust architecture design +- Identify gaps, opportunities, and risks +- Define success metrics: Microsegmentation Coverage %, Identity Verification Rate, Continuous Authentication Score, Lateral Movement Prevention Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the zero trust architecture design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never trust, always verify — apply to internal traffic, not just perimeter + +## Output Format + +```markdown +# Zero Trust Architecture Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- NIST SP 800-207 +- CISA Zero Trust Maturity Model +- Google BeyondCorp +- Microsoft Zero Trust Model +- Forrester ZTX +- DoD Zero Trust Reference Architecture + +## Key Metrics +- Microsegmentation Coverage % +- Identity Verification Rate +- Continuous Authentication Score +- Lateral Movement Prevention Rate +- Policy Decision Point Response Time +- Zero Trust Maturity Level + +## Best Practices +- Never trust, always verify — apply to internal traffic, not just perimeter +- Implement microsegmentation starting with crown jewel assets +- Deploy identity-aware proxies for all application access +- Encrypt all traffic (east-west and north-south) regardless of network location +- Implement continuous posture assessment for all endpoints + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/ab-test-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/ab-test-analysis/SKILL.md new file mode 100644 index 0000000..18114f6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/ab-test-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a ab test analysis with structured process, quality checks, and system integration +--- + +# Ab Test Analysis + +## Purpose + +Analyze and produce a comprehensive ab test analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ab test analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ab test analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ab test analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Ab Test Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/analytics-implementation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/data/analytics-implementation-plan/SKILL.md new file mode 100644 index 0000000..60b2fcf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/analytics-implementation-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a analytics implementation plan with structured process, quality checks, and system integration +--- + +# Analytics Implementation Plan + +## Purpose + +Design and document a comprehensive analytics implementation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing analytics implementation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the analytics implementation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the analytics implementation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Analytics Implementation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/attribution-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/attribution-analysis/SKILL.md new file mode 100644 index 0000000..93a3b13 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/attribution-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a attribution analysis with structured process, quality checks, and system integration +--- + +# Attribution Analysis + +## Purpose + +Analyze and produce a comprehensive attribution analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing attribution analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the attribution analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the attribution analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Attribution Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/benchmark-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/benchmark-analysis/SKILL.md new file mode 100644 index 0000000..b99cca9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/benchmark-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a benchmark analysis with structured process, quality checks, and system integration +--- + +# Benchmark Analysis + +## Purpose + +Analyze and produce a comprehensive benchmark analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing benchmark analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the benchmark analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the benchmark analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Benchmark Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/chart-selection-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/data/chart-selection-guide/SKILL.md new file mode 100644 index 0000000..825a4b8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/chart-selection-guide/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a chart selection guide with structured process, quality checks, and system integration +--- + +# Chart Selection Guide + +## Purpose + +Design and document a comprehensive chart selection guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chart selection guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chart selection guide +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chart selection guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Chart Selection Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/clustering-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/clustering-analysis/SKILL.md new file mode 100644 index 0000000..2138b1f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/clustering-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a clustering analysis with structured process, quality checks, and system integration +--- + +# Clustering Analysis + +## Purpose + +Analyze and produce a comprehensive clustering analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing clustering analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the clustering analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the clustering analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Clustering Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/cohort-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/cohort-analysis/SKILL.md new file mode 100644 index 0000000..78fcce8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/cohort-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a cohort analysis with structured process, quality checks, and system integration +--- + +# Cohort Analysis + +## Purpose + +Analyze and produce a comprehensive cohort analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cohort analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cohort analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cohort analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Cohort Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/competitive-data-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/competitive-data-analysis/SKILL.md new file mode 100644 index 0000000..40af198 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/competitive-data-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a competitive data analysis with structured process, quality checks, and system integration +--- + +# Competitive Data Analysis + +## Purpose + +Analyze and produce a comprehensive competitive data analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitive data analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitive data analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitive data analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Competitive Data Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/customer-segmentation/SKILL.md b/clowdex-download/.claude/.claude/skills/data/customer-segmentation/SKILL.md new file mode 100644 index 0000000..a8bf960 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/customer-segmentation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a customer segmentation with structured process, quality checks, and system integration +--- + +# Customer Segmentation + +## Purpose + +Create a comprehensive customer segmentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer segmentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer segmentation +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer segmentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Customer Segmentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/dashboard-design/SKILL.md b/clowdex-download/.claude/.claude/skills/data/dashboard-design/SKILL.md new file mode 100644 index 0000000..4e75225 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/dashboard-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a dashboard design with structured process, quality checks, and system integration +--- + +# Dashboard Design + +## Purpose + +Analyze and produce a comprehensive dashboard design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dashboard design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dashboard design +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dashboard design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Dashboard Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-access-control/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-access-control/SKILL.md new file mode 100644 index 0000000..78e2bbc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-access-control/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data access control with structured process, quality checks, and system integration +--- + +# Data Access Control + +## Purpose + +Create a comprehensive data access control that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data access control documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data access control +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data access control using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Access Control + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-analysis-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-analysis-plan/SKILL.md new file mode 100644 index 0000000..910541f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-analysis-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a data analysis plan with structured process, quality checks, and system integration +--- + +# Data Analysis Plan + +## Purpose + +Analyze and produce a comprehensive data analysis plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data analysis plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data analysis plan +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data analysis plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Analysis Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-catalog/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-catalog/SKILL.md new file mode 100644 index 0000000..c5c5e88 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-catalog/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data catalog with structured process, quality checks, and system integration +--- + +# Data Catalog + +## Purpose + +Create a comprehensive data catalog that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data catalog documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data catalog +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data catalog using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Catalog + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-cleaning-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-cleaning-plan/SKILL.md new file mode 100644 index 0000000..cbab8ca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-cleaning-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a data cleaning plan with structured process, quality checks, and system integration +--- + +# Data Cleaning Plan + +## Purpose + +Design and document a comprehensive data cleaning plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data cleaning plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data cleaning plan +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data cleaning plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Cleaning Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-dictionary/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-dictionary/SKILL.md new file mode 100644 index 0000000..f19a74a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-dictionary/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data dictionary with structured process, quality checks, and system integration +--- + +# Data Dictionary + +## Purpose + +Create a comprehensive data dictionary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data dictionary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data dictionary +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data dictionary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Dictionary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-driven-recommendation/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-driven-recommendation/SKILL.md new file mode 100644 index 0000000..452364f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-driven-recommendation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data driven recommendation with structured process, quality checks, and system integration +--- + +# Data Driven Recommendation + +## Purpose + +Create a comprehensive data driven recommendation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data driven recommendation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data driven recommendation +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data driven recommendation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Driven Recommendation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-governance-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-governance-policy/SKILL.md new file mode 100644 index 0000000..3a8d5ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-governance-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data governance policy with structured process, quality checks, and system integration +--- + +# Data Governance Policy + +## Purpose + +Create a comprehensive data governance policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data governance policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data governance policy +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data governance policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Governance Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-mart-design/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-mart-design/SKILL.md new file mode 100644 index 0000000..c948404 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-mart-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data mart design with structured process, quality checks, and system integration +--- + +# Data Mart Design + +## Purpose + +Create a comprehensive data mart design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data mart design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data mart design +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data mart design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Mart Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-privacy-impact/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-privacy-impact/SKILL.md new file mode 100644 index 0000000..5bd9d99 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-privacy-impact/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data privacy impact with structured process, quality checks, and system integration +--- + +# Data Privacy Impact + +## Purpose + +Create a comprehensive data privacy impact that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data privacy impact documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data privacy impact +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data privacy impact using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Privacy Impact + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-quality-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-quality-audit/SKILL.md new file mode 100644 index 0000000..149fbe2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-quality-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a data quality audit with structured process, quality checks, and system integration +--- + +# Data Quality Audit + +## Purpose + +Analyze and produce a comprehensive data quality audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data quality audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data quality audit +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data quality audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Quality Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-storytelling/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-storytelling/SKILL.md new file mode 100644 index 0000000..aec02ec --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-storytelling/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data storytelling with structured process, quality checks, and system integration +--- + +# Data Storytelling + +## Purpose + +Create a comprehensive data storytelling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data storytelling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data storytelling +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data storytelling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Storytelling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-validation/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-validation/SKILL.md new file mode 100644 index 0000000..c1d1456 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-validation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data validation with structured process, quality checks, and system integration +--- + +# Data Validation + +## Purpose + +Create a comprehensive data validation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data validation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data validation +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data validation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Validation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-visualization/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-visualization/SKILL.md new file mode 100644 index 0000000..a3d75f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-visualization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data visualization with structured process, quality checks, and system integration +--- + +# Data Visualization + +## Purpose + +Create a comprehensive data visualization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data visualization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data visualization +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data visualization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Visualization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/data-warehouse-schema/SKILL.md b/clowdex-download/.claude/.claude/skills/data/data-warehouse-schema/SKILL.md new file mode 100644 index 0000000..851f88a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/data-warehouse-schema/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data warehouse schema with structured process, quality checks, and system integration +--- + +# Data Warehouse Schema + +## Purpose + +Create a comprehensive data warehouse schema that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data warehouse schema documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data warehouse schema +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data warehouse schema using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Data Warehouse Schema + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/database-performance/SKILL.md b/clowdex-download/.claude/.claude/skills/data/database-performance/SKILL.md new file mode 100644 index 0000000..3a346cc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/database-performance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a database performance with structured process, quality checks, and system integration +--- + +# Database Performance + +## Purpose + +Create a comprehensive database performance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing database performance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the database performance +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the database performance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Database Performance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/etl-pipeline-design/SKILL.md b/clowdex-download/.claude/.claude/skills/data/etl-pipeline-design/SKILL.md new file mode 100644 index 0000000..79bf6d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/etl-pipeline-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a etl pipeline design with structured process, quality checks, and system integration +--- + +# Etl Pipeline Design + +## Purpose + +Create a comprehensive etl pipeline design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing etl pipeline design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the etl pipeline design +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the etl pipeline design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Etl Pipeline Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/event-taxonomy/SKILL.md b/clowdex-download/.claude/.claude/skills/data/event-taxonomy/SKILL.md new file mode 100644 index 0000000..466aa6b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/event-taxonomy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a event taxonomy with structured process, quality checks, and system integration +--- + +# Event Taxonomy + +## Purpose + +Create a comprehensive event taxonomy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event taxonomy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event taxonomy +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event taxonomy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Event Taxonomy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/executive-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/data/executive-dashboard/SKILL.md new file mode 100644 index 0000000..1e90dfc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/executive-dashboard/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a executive dashboard with structured process, quality checks, and system integration +--- + +# Executive Dashboard + +## Purpose + +Analyze and produce a comprehensive executive dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Executive Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/experiment-results/SKILL.md b/clowdex-download/.claude/.claude/skills/data/experiment-results/SKILL.md new file mode 100644 index 0000000..75517e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/experiment-results/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a experiment results with structured process, quality checks, and system integration +--- + +# Experiment Results + +## Purpose + +Create a comprehensive experiment results that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing experiment results documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the experiment results +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the experiment results using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Experiment Results + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/exploratory-data-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/exploratory-data-analysis/SKILL.md new file mode 100644 index 0000000..27d2d8a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/exploratory-data-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a exploratory data analysis with structured process, quality checks, and system integration +--- + +# Exploratory Data Analysis + +## Purpose + +Analyze and produce a comprehensive exploratory data analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing exploratory data analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the exploratory data analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the exploratory data analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Exploratory Data Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/forecasting-model/SKILL.md b/clowdex-download/.claude/.claude/skills/data/forecasting-model/SKILL.md new file mode 100644 index 0000000..ee6890b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/forecasting-model/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a forecasting model with structured process, quality checks, and system integration +--- + +# Forecasting Model + +## Purpose + +Analyze and produce a comprehensive forecasting model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing forecasting model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the forecasting model +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the forecasting model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Forecasting Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/funnel-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/funnel-analysis/SKILL.md new file mode 100644 index 0000000..227e71f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/funnel-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a funnel analysis with structured process, quality checks, and system integration +--- + +# Funnel Analysis + +## Purpose + +Analyze and produce a comprehensive funnel analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing funnel analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the funnel analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the funnel analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Funnel Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/incrementality-test/SKILL.md b/clowdex-download/.claude/.claude/skills/data/incrementality-test/SKILL.md new file mode 100644 index 0000000..f95fe39 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/incrementality-test/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a incrementality test with structured process, quality checks, and system integration +--- + +# Incrementality Test + +## Purpose + +Create a comprehensive incrementality test that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incrementality test documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incrementality test +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incrementality test using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Incrementality Test + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/industry-data-report/SKILL.md b/clowdex-download/.claude/.claude/skills/data/industry-data-report/SKILL.md new file mode 100644 index 0000000..b03cc96 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/industry-data-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a industry data report with structured process, quality checks, and system integration +--- + +# Industry Data Report + +## Purpose + +Analyze and produce a comprehensive industry data report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing industry data report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the industry data report +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the industry data report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Industry Data Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/infographic-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/data/infographic-spec/SKILL.md new file mode 100644 index 0000000..43eada0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/infographic-spec/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a infographic spec with structured process, quality checks, and system integration +--- + +# Infographic Spec + +## Purpose + +Create a comprehensive infographic spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing infographic spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the infographic spec +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the infographic spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Infographic Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/insight-presentation/SKILL.md b/clowdex-download/.claude/.claude/skills/data/insight-presentation/SKILL.md new file mode 100644 index 0000000..f239bcc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/insight-presentation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a insight presentation with structured process, quality checks, and system integration +--- + +# Insight Presentation + +## Purpose + +Create a comprehensive insight presentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing insight presentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the insight presentation +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the insight presentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Insight Presentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/kpi-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/data/kpi-dashboard/SKILL.md new file mode 100644 index 0000000..c837cb3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/kpi-dashboard/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a kpi dashboard with structured process, quality checks, and system integration +--- + +# Kpi Dashboard + +## Purpose + +Analyze and produce a comprehensive kpi dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kpi dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kpi dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kpi dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Kpi Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/marketing-mix-model/SKILL.md b/clowdex-download/.claude/.claude/skills/data/marketing-mix-model/SKILL.md new file mode 100644 index 0000000..c3af377 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/marketing-mix-model/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a marketing mix model with structured process, quality checks, and system integration +--- + +# Marketing Mix Model + +## Purpose + +Design and document a comprehensive marketing mix model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing mix model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing mix model +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing mix model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Marketing Mix Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/metadata-management/SKILL.md b/clowdex-download/.claude/.claude/skills/data/metadata-management/SKILL.md new file mode 100644 index 0000000..83fc99c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/metadata-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a metadata management with structured process, quality checks, and system integration +--- + +# Metadata Management + +## Purpose + +Create a comprehensive metadata management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing metadata management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the metadata management +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the metadata management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Metadata Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/ml-experiment-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/data/ml-experiment-plan/SKILL.md new file mode 100644 index 0000000..fd2a79f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/ml-experiment-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a ml experiment plan with structured process, quality checks, and system integration +--- + +# Ml Experiment Plan + +## Purpose + +Design and document a comprehensive ml experiment plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ml experiment plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ml experiment plan +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ml experiment plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Ml Experiment Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/model-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/data/model-evaluation/SKILL.md new file mode 100644 index 0000000..b303bbb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/model-evaluation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a model evaluation with structured process, quality checks, and system integration +--- + +# Model Evaluation + +## Purpose + +Analyze and produce a comprehensive model evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing model evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the model evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the model evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Model Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/monthly-report/SKILL.md b/clowdex-download/.claude/.claude/skills/data/monthly-report/SKILL.md new file mode 100644 index 0000000..79c4b75 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/monthly-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a monthly report with structured process, quality checks, and system integration +--- + +# Monthly Report + +## Purpose + +Analyze and produce a comprehensive monthly report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing monthly report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the monthly report +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the monthly report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Monthly Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/nps-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/nps-analysis/SKILL.md new file mode 100644 index 0000000..374bf3b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/nps-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a nps analysis with structured process, quality checks, and system integration +--- + +# Nps Analysis + +## Purpose + +Analyze and produce a comprehensive nps analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nps analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nps analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nps analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Nps Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/predictive-model-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/data/predictive-model-spec/SKILL.md new file mode 100644 index 0000000..24a5462 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/predictive-model-spec/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a predictive model spec with structured process, quality checks, and system integration +--- + +# Predictive Model Spec + +## Purpose + +Design and document a comprehensive predictive model spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing predictive model spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the predictive model spec +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the predictive model spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Predictive Model Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/query-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/data/query-optimization/SKILL.md new file mode 100644 index 0000000..4c6830e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/query-optimization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a query optimization with structured process, quality checks, and system integration +--- + +# Query Optimization + +## Purpose + +Create a comprehensive query optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing query optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the query optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the query optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Query Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/report-template/SKILL.md b/clowdex-download/.claude/.claude/skills/data/report-template/SKILL.md new file mode 100644 index 0000000..58d318d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/report-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a report template with structured process, quality checks, and system integration +--- + +# Report Template + +## Purpose + +Analyze and produce a comprehensive report template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing report template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the report template +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the report template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Report Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/retention-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/retention-analysis/SKILL.md new file mode 100644 index 0000000..3011eb6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/retention-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a retention analysis with structured process, quality checks, and system integration +--- + +# Retention Analysis + +## Purpose + +Analyze and produce a comprehensive retention analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retention analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retention analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retention analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Retention Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/rfm-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/rfm-analysis/SKILL.md new file mode 100644 index 0000000..84704ab --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/rfm-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a rfm analysis with structured process, quality checks, and system integration +--- + +# Rfm Analysis + +## Purpose + +Analyze and produce a comprehensive rfm analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rfm analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rfm analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rfm analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Rfm Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/sql-query-builder/SKILL.md b/clowdex-download/.claude/.claude/skills/data/sql-query-builder/SKILL.md new file mode 100644 index 0000000..c8d5bf4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/sql-query-builder/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a sql query builder with structured process, quality checks, and system integration +--- + +# Sql Query Builder + +## Purpose + +Create a comprehensive sql query builder that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sql query builder documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sql query builder +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sql query builder using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Sql Query Builder + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/statistical-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/statistical-analysis/SKILL.md new file mode 100644 index 0000000..b74372a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/statistical-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a statistical analysis with structured process, quality checks, and system integration +--- + +# Statistical Analysis + +## Purpose + +Analyze and produce a comprehensive statistical analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing statistical analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the statistical analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the statistical analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Statistical Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/statistical-significance/SKILL.md b/clowdex-download/.claude/.claude/skills/data/statistical-significance/SKILL.md new file mode 100644 index 0000000..0814145 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/statistical-significance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a statistical significance with structured process, quality checks, and system integration +--- + +# Statistical Significance + +## Purpose + +Create a comprehensive statistical significance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing statistical significance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the statistical significance +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the statistical significance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Statistical Significance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/survey-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/survey-analysis/SKILL.md new file mode 100644 index 0000000..3613773 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/survey-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a survey analysis with structured process, quality checks, and system integration +--- + +# Survey Analysis + +## Purpose + +Analyze and produce a comprehensive survey analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing survey analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the survey analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the survey analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Survey Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/survey-design/SKILL.md b/clowdex-download/.claude/.claude/skills/data/survey-design/SKILL.md new file mode 100644 index 0000000..872c89e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/survey-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a survey design with structured process, quality checks, and system integration +--- + +# Survey Design + +## Purpose + +Create a comprehensive survey design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing survey design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the survey design +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the survey design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Survey Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/time-series-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/time-series-analysis/SKILL.md new file mode 100644 index 0000000..17f7de2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/time-series-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a time series analysis with structured process, quality checks, and system integration +--- + +# Time Series Analysis + +## Purpose + +Analyze and produce a comprehensive time series analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing time series analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the time series analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the time series analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Time Series Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/tracking-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/data/tracking-plan/SKILL.md new file mode 100644 index 0000000..808d9c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/tracking-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a tracking plan with structured process, quality checks, and system integration +--- + +# Tracking Plan + +## Purpose + +Design and document a comprehensive tracking plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tracking plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tracking plan +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tracking plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Tracking Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/trend-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/data/trend-analysis/SKILL.md new file mode 100644 index 0000000..7be7ea9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/trend-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a trend analysis with structured process, quality checks, and system integration +--- + +# Trend Analysis + +## Purpose + +Analyze and produce a comprehensive trend analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trend analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trend analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trend analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Trend Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/data/weekly-report/SKILL.md b/clowdex-download/.claude/.claude/skills/data/weekly-report/SKILL.md new file mode 100644 index 0000000..5a415ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/data/weekly-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a weekly report with structured process, quality checks, and system integration +--- + +# Weekly Report + +## Purpose + +Analyze and produce a comprehensive weekly report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Data & Analytics + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing weekly report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: CRISP-DM, Kimball Dimensional Modeling, Data Mesh + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the weekly report +- Identify gaps, opportunities, and risks +- Define success metrics: Data Quality Score, Query Performance, Dashboard Load Time, Data Freshness +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the weekly report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Define metrics before building dashboards + +## Output Format + +```markdown +# Weekly Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- CRISP-DM +- Kimball Dimensional Modeling +- Data Mesh +- Data Vault +- Metrics Layer + +## Key Metrics +- Data Quality Score +- Query Performance +- Dashboard Load Time +- Data Freshness +- Coverage Rate +- Anomaly Detection Rate + +## Best Practices +- Define metrics before building dashboards +- One source of truth per metric +- Document all transformations and business logic +- Test data pipelines like you test code +- Archive raw data, transform in layers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/accessibility-design-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/accessibility-design-guide/SKILL.md new file mode 100644 index 0000000..05d4adb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/accessibility-design-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a accessibility design guide with structured process, quality checks, and system integration +--- + +# Accessibility Design Guide + +## Purpose + +Create a comprehensive accessibility design guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing accessibility design guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the accessibility design guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the accessibility design guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Accessibility Design Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/animation-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/animation-brief/SKILL.md new file mode 100644 index 0000000..4569565 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/animation-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a animation brief with structured process, quality checks, and system integration +--- + +# Animation Brief + +## Purpose + +Create a comprehensive animation brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing animation brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the animation brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the animation brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Animation Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/art-direction-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/art-direction-guide/SKILL.md new file mode 100644 index 0000000..204c44f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/art-direction-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a art direction guide with structured process, quality checks, and system integration +--- + +# Art Direction Guide + +## Purpose + +Design and document a comprehensive art direction guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing art direction guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the art direction guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the art direction guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Art Direction Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/brand-application-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/brand-application-guide/SKILL.md new file mode 100644 index 0000000..041e375 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/brand-application-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a brand application guide with structured process, quality checks, and system integration +--- + +# Brand Application Guide + +## Purpose + +Design and document a comprehensive brand application guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand application guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand application guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand application guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Brand Application Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/brand-asset-library/SKILL.md b/clowdex-download/.claude/.claude/skills/design/brand-asset-library/SKILL.md new file mode 100644 index 0000000..3642637 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/brand-asset-library/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a brand asset library with structured process, quality checks, and system integration +--- + +# Brand Asset Library + +## Purpose + +Create a comprehensive brand asset library that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand asset library documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand asset library +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand asset library using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Brand Asset Library + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/brand-guidelines-doc/SKILL.md b/clowdex-download/.claude/.claude/skills/design/brand-guidelines-doc/SKILL.md new file mode 100644 index 0000000..9fa151b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/brand-guidelines-doc/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a brand guidelines doc with structured process, quality checks, and system integration +--- + +# Brand Guidelines Doc + +## Purpose + +Design and document a comprehensive brand guidelines doc that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand guidelines doc documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand guidelines doc +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand guidelines doc using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Brand Guidelines Doc + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/brand-identity-system/SKILL.md b/clowdex-download/.claude/.claude/skills/design/brand-identity-system/SKILL.md new file mode 100644 index 0000000..5fd86a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/brand-identity-system/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a brand identity system with structured process, quality checks, and system integration +--- + +# Brand Identity System + +## Purpose + +Design and document a comprehensive brand identity system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand identity system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand identity system +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand identity system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Brand Identity System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/campaign-creative-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/campaign-creative-brief/SKILL.md new file mode 100644 index 0000000..359864f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/campaign-creative-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a campaign creative brief with structured process, quality checks, and system integration +--- + +# Campaign Creative Brief + +## Purpose + +Create a comprehensive campaign creative brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing campaign creative brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the campaign creative brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the campaign creative brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Campaign Creative Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/color-palette-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/color-palette-guide/SKILL.md new file mode 100644 index 0000000..f4b992d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/color-palette-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a color palette guide with structured process, quality checks, and system integration +--- + +# Color Palette Guide + +## Purpose + +Design and document a comprehensive color palette guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing color palette guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the color palette guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the color palette guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Color Palette Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/component-library-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/design/component-library-spec/SKILL.md new file mode 100644 index 0000000..b1e44ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/component-library-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a component library spec with structured process, quality checks, and system integration +--- + +# Component Library Spec + +## Purpose + +Create a comprehensive component library spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing component library spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the component library spec +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the component library spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Component Library Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/creative-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/creative-brief/SKILL.md new file mode 100644 index 0000000..b5d5929 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/creative-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a creative brief with structured process, quality checks, and system integration +--- + +# Creative Brief + +## Purpose + +Create a comprehensive creative brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing creative brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the creative brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the creative brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Creative Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/creative-campaign-concept/SKILL.md b/clowdex-download/.claude/.claude/skills/design/creative-campaign-concept/SKILL.md new file mode 100644 index 0000000..1fba80b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/creative-campaign-concept/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a creative campaign concept with structured process, quality checks, and system integration +--- + +# Creative Campaign Concept + +## Purpose + +Design and document a comprehensive creative campaign concept that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing creative campaign concept documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the creative campaign concept +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the creative campaign concept using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Creative Campaign Concept + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/creative-review-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/design/creative-review-checklist/SKILL.md new file mode 100644 index 0000000..c18a0fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/creative-review-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a creative review checklist with structured process, quality checks, and system integration +--- + +# Creative Review Checklist + +## Purpose + +Analyze and produce a comprehensive creative review checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing creative review checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the creative review checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the creative review checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Creative Review Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/data-visualization-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/data-visualization-guide/SKILL.md new file mode 100644 index 0000000..c3b495f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/data-visualization-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a data visualization guide with structured process, quality checks, and system integration +--- + +# Data Visualization Guide + +## Purpose + +Design and document a comprehensive data visualization guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data visualization guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data visualization guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data visualization guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Data Visualization Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-brief/SKILL.md new file mode 100644 index 0000000..e8e4ec5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design brief with structured process, quality checks, and system integration +--- + +# Design Brief + +## Purpose + +Create a comprehensive design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-critique-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-critique-guide/SKILL.md new file mode 100644 index 0000000..069c1fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-critique-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design critique guide with structured process, quality checks, and system integration +--- + +# Design Critique Guide + +## Purpose + +Create a comprehensive design critique guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design critique guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design critique guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design critique guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Critique Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-handoff/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-handoff/SKILL.md new file mode 100644 index 0000000..29e27cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-handoff/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design handoff with structured process, quality checks, and system integration +--- + +# Design Handoff + +## Purpose + +Create a comprehensive design handoff that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design handoff documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design handoff +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design handoff using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Handoff + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-sprint/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-sprint/SKILL.md new file mode 100644 index 0000000..a400c74 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-sprint/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design sprint with structured process, quality checks, and system integration +--- + +# Design Sprint + +## Purpose + +Create a comprehensive design sprint that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design sprint documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design sprint +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design sprint using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Sprint + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-system/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-system/SKILL.md new file mode 100644 index 0000000..2bd7013 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-system/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design system with structured process, quality checks, and system integration +--- + +# Design System + +## Purpose + +Create a comprehensive design system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design system +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-thinking-workshop/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-thinking-workshop/SKILL.md new file mode 100644 index 0000000..5f5c4f7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-thinking-workshop/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design thinking workshop with structured process, quality checks, and system integration +--- + +# Design Thinking Workshop + +## Purpose + +Create a comprehensive design thinking workshop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design thinking workshop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design thinking workshop +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design thinking workshop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Thinking Workshop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/design-tokens/SKILL.md b/clowdex-download/.claude/.claude/skills/design/design-tokens/SKILL.md new file mode 100644 index 0000000..a1e61ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/design-tokens/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a design tokens with structured process, quality checks, and system integration +--- + +# Design Tokens + +## Purpose + +Create a comprehensive design tokens that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing design tokens documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the design tokens +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the design tokens using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Design Tokens + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/email-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/email-design-brief/SKILL.md new file mode 100644 index 0000000..2ba4a83 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/email-design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a email design brief with structured process, quality checks, and system integration +--- + +# Email Design Brief + +## Purpose + +Create a comprehensive email design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Email Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/icon-system/SKILL.md b/clowdex-download/.claude/.claude/skills/design/icon-system/SKILL.md new file mode 100644 index 0000000..2c0dd1d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/icon-system/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a icon system with structured process, quality checks, and system integration +--- + +# Icon System + +## Purpose + +Design and document a comprehensive icon system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing icon system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the icon system +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the icon system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Icon System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/ideation-session/SKILL.md b/clowdex-download/.claude/.claude/skills/design/ideation-session/SKILL.md new file mode 100644 index 0000000..e4a7545 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/ideation-session/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ideation session with structured process, quality checks, and system integration +--- + +# Ideation Session + +## Purpose + +Create a comprehensive ideation session that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ideation session documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ideation session +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ideation session using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Ideation Session + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/illustration-style-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/illustration-style-guide/SKILL.md new file mode 100644 index 0000000..e097a77 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/illustration-style-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a illustration style guide with structured process, quality checks, and system integration +--- + +# Illustration Style Guide + +## Purpose + +Design and document a comprehensive illustration style guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing illustration style guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the illustration style guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the illustration style guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Illustration Style Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/inclusive-design-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/design/inclusive-design-checklist/SKILL.md new file mode 100644 index 0000000..c368f18 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/inclusive-design-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a inclusive design checklist with structured process, quality checks, and system integration +--- + +# Inclusive Design Checklist + +## Purpose + +Analyze and produce a comprehensive inclusive design checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inclusive design checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inclusive design checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inclusive design checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Inclusive Design Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/infographic-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/infographic-brief/SKILL.md new file mode 100644 index 0000000..cea9832 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/infographic-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a infographic brief with structured process, quality checks, and system integration +--- + +# Infographic Brief + +## Purpose + +Create a comprehensive infographic brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing infographic brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the infographic brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the infographic brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Infographic Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/information-architecture/SKILL.md b/clowdex-download/.claude/.claude/skills/design/information-architecture/SKILL.md new file mode 100644 index 0000000..df3312d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/information-architecture/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a information architecture with structured process, quality checks, and system integration +--- + +# Information Architecture + +## Purpose + +Create a comprehensive information architecture that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing information architecture documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the information architecture +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the information architecture using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Information Architecture + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/interaction-design-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/design/interaction-design-spec/SKILL.md new file mode 100644 index 0000000..8d3cd8f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/interaction-design-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a interaction design spec with structured process, quality checks, and system integration +--- + +# Interaction Design Spec + +## Purpose + +Create a comprehensive interaction design spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interaction design spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interaction design spec +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interaction design spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Interaction Design Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/landing-page-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/landing-page-design-brief/SKILL.md new file mode 100644 index 0000000..b407abf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/landing-page-design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a landing page design brief with structured process, quality checks, and system integration +--- + +# Landing Page Design Brief + +## Purpose + +Create a comprehensive landing page design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing landing page design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the landing page design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the landing page design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Landing Page Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/logo-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/logo-brief/SKILL.md new file mode 100644 index 0000000..6a6cc7d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/logo-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a logo brief with structured process, quality checks, and system integration +--- + +# Logo Brief + +## Purpose + +Create a comprehensive logo brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing logo brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the logo brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the logo brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Logo Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/mobile-design-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/mobile-design-guide/SKILL.md new file mode 100644 index 0000000..25c2a96 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/mobile-design-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mobile design guide with structured process, quality checks, and system integration +--- + +# Mobile Design Guide + +## Purpose + +Create a comprehensive mobile design guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mobile design guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mobile design guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mobile design guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Mobile Design Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/mood-board/SKILL.md b/clowdex-download/.claude/.claude/skills/design/mood-board/SKILL.md new file mode 100644 index 0000000..282a8af --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/mood-board/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mood board with structured process, quality checks, and system integration +--- + +# Mood Board + +## Purpose + +Create a comprehensive mood board that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mood board documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mood board +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mood board using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Mood Board + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/packaging-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/packaging-design-brief/SKILL.md new file mode 100644 index 0000000..138a4d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/packaging-design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a packaging design brief with structured process, quality checks, and system integration +--- + +# Packaging Design Brief + +## Purpose + +Create a comprehensive packaging design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing packaging design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the packaging design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the packaging design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Packaging Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/persona-ux/SKILL.md b/clowdex-download/.claude/.claude/skills/design/persona-ux/SKILL.md new file mode 100644 index 0000000..37cfa36 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/persona-ux/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a persona ux with structured process, quality checks, and system integration +--- + +# Persona Ux + +## Purpose + +Create a comprehensive persona ux that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing persona ux documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the persona ux +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the persona ux using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Persona Ux + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/photo-direction-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/photo-direction-brief/SKILL.md new file mode 100644 index 0000000..8d1d06e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/photo-direction-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a photo direction brief with structured process, quality checks, and system integration +--- + +# Photo Direction Brief + +## Purpose + +Create a comprehensive photo direction brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing photo direction brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the photo direction brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the photo direction brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Photo Direction Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/presentation-design-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/presentation-design-guide/SKILL.md new file mode 100644 index 0000000..7045bd5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/presentation-design-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a presentation design guide with structured process, quality checks, and system integration +--- + +# Presentation Design Guide + +## Purpose + +Create a comprehensive presentation design guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing presentation design guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the presentation design guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the presentation design guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Presentation Design Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/print-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/print-design-brief/SKILL.md new file mode 100644 index 0000000..9c586e4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/print-design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a print design brief with structured process, quality checks, and system integration +--- + +# Print Design Brief + +## Purpose + +Create a comprehensive print design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing print design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the print design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the print design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Print Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/prototype-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/design/prototype-spec/SKILL.md new file mode 100644 index 0000000..0d15001 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/prototype-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a prototype spec with structured process, quality checks, and system integration +--- + +# Prototype Spec + +## Purpose + +Create a comprehensive prototype spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prototype spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prototype spec +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prototype spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Prototype Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/responsive-design-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/design/responsive-design-spec/SKILL.md new file mode 100644 index 0000000..aa44e52 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/responsive-design-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a responsive design spec with structured process, quality checks, and system integration +--- + +# Responsive Design Spec + +## Purpose + +Create a comprehensive responsive design spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing responsive design spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the responsive design spec +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the responsive design spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Responsive Design Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/signage-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/signage-brief/SKILL.md new file mode 100644 index 0000000..dba8461 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/signage-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a signage brief with structured process, quality checks, and system integration +--- + +# Signage Brief + +## Purpose + +Create a comprehensive signage brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing signage brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the signage brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the signage brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Signage Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/social-media-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/social-media-design-brief/SKILL.md new file mode 100644 index 0000000..facc2cc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/social-media-design-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a social media design brief with structured process, quality checks, and system integration +--- + +# Social Media Design Brief + +## Purpose + +Create a comprehensive social media design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Social Media Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/storyboard/SKILL.md b/clowdex-download/.claude/.claude/skills/design/storyboard/SKILL.md new file mode 100644 index 0000000..690d372 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/storyboard/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a storyboard with structured process, quality checks, and system integration +--- + +# Storyboard + +## Purpose + +Create a comprehensive storyboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing storyboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the storyboard +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the storyboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Storyboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/style-tile/SKILL.md b/clowdex-download/.claude/.claude/skills/design/style-tile/SKILL.md new file mode 100644 index 0000000..cb0966c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/style-tile/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a style tile with structured process, quality checks, and system integration +--- + +# Style Tile + +## Purpose + +Create a comprehensive style tile that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing style tile documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the style tile +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the style tile using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Style Tile + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/tablet-design-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/design/tablet-design-guide/SKILL.md new file mode 100644 index 0000000..963e717 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/tablet-design-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a tablet design guide with structured process, quality checks, and system integration +--- + +# Tablet Design Guide + +## Purpose + +Create a comprehensive tablet design guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tablet design guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tablet design guide +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tablet design guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Tablet Design Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/typography-system/SKILL.md b/clowdex-download/.claude/.claude/skills/design/typography-system/SKILL.md new file mode 100644 index 0000000..7d04ec1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/typography-system/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a typography system with structured process, quality checks, and system integration +--- + +# Typography System + +## Purpose + +Design and document a comprehensive typography system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing typography system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the typography system +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the typography system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Typography System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/usability-test/SKILL.md b/clowdex-download/.claude/.claude/skills/design/usability-test/SKILL.md new file mode 100644 index 0000000..1a0b3ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/usability-test/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a usability test with structured process, quality checks, and system integration +--- + +# Usability Test + +## Purpose + +Create a comprehensive usability test that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing usability test documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the usability test +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the usability test using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Usability Test + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/user-flow/SKILL.md b/clowdex-download/.claude/.claude/skills/design/user-flow/SKILL.md new file mode 100644 index 0000000..8f36a41 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/user-flow/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a user flow with structured process, quality checks, and system integration +--- + +# User Flow + +## Purpose + +Create a comprehensive user flow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user flow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user flow +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user flow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# User Flow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/user-interview-ux/SKILL.md b/clowdex-download/.claude/.claude/skills/design/user-interview-ux/SKILL.md new file mode 100644 index 0000000..186e5dd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/user-interview-ux/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a user interview ux with structured process, quality checks, and system integration +--- + +# User Interview Ux + +## Purpose + +Create a comprehensive user interview ux that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user interview ux documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user interview ux +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user interview ux using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# User Interview Ux + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/ux-research-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/design/ux-research-plan/SKILL.md new file mode 100644 index 0000000..5877097 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/ux-research-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a ux research plan with structured process, quality checks, and system integration +--- + +# Ux Research Plan + +## Purpose + +Design and document a comprehensive ux research plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ux research plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ux research plan +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ux research plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Ux Research Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/video-direction-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/design/video-direction-brief/SKILL.md new file mode 100644 index 0000000..84ad847 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/video-direction-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a video direction brief with structured process, quality checks, and system integration +--- + +# Video Direction Brief + +## Purpose + +Create a comprehensive video direction brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing video direction brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the video direction brief +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the video direction brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Video Direction Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/visual-direction/SKILL.md b/clowdex-download/.claude/.claude/skills/design/visual-direction/SKILL.md new file mode 100644 index 0000000..71ba7c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/visual-direction/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a visual direction with structured process, quality checks, and system integration +--- + +# Visual Direction + +## Purpose + +Create a comprehensive visual direction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing visual direction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the visual direction +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the visual direction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Visual Direction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/wcag-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/design/wcag-audit/SKILL.md new file mode 100644 index 0000000..94ed818 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/wcag-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a wcag audit with structured process, quality checks, and system integration +--- + +# Wcag Audit + +## Purpose + +Analyze and produce a comprehensive wcag audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wcag audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wcag audit +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wcag audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Wcag Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/design/wireframe-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/design/wireframe-spec/SKILL.md new file mode 100644 index 0000000..7c586c7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/design/wireframe-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a wireframe spec with structured process, quality checks, and system integration +--- + +# Wireframe Spec + +## Purpose + +Create a comprehensive wireframe spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Design & Creative + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wireframe spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Design Thinking (5 stages), Double Diamond, Atomic Design + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wireframe spec +- Identify gaps, opportunities, and risks +- Define success metrics: Task Completion Rate, Time on Task, Error Rate, System Usability Scale (SUS) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wireframe spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with user research, not aesthetics + +## Output Format + +```markdown +# Wireframe Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Design Thinking (5 stages) +- Double Diamond +- Atomic Design +- Design Sprint +- Material Design / Human Interface Guidelines +- WCAG 2.1 AA + +## Key Metrics +- Task Completion Rate +- Time on Task +- Error Rate +- System Usability Scale (SUS) +- Accessibility Score +- Design System Adoption Rate + +## Best Practices +- Start with user research, not aesthetics +- Maintain a living design system +- Test with 5 users to find 85% of usability issues +- Accessibility is not optional — design for it from day one +- Document design decisions and rationale + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/accessibility-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/development/accessibility-audit/SKILL.md new file mode 100644 index 0000000..2df965b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/accessibility-audit/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a accessibility audit with structured process, quality checks, and system integration +--- + +# Accessibility Audit + +## Purpose + +Analyze and produce a comprehensive accessibility audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing accessibility audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the accessibility audit +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the accessibility audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Accessibility Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/alerting-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/alerting-strategy/SKILL.md new file mode 100644 index 0000000..e969385 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/alerting-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a alerting strategy with structured process, quality checks, and system integration +--- + +# Alerting Strategy + +## Purpose + +Design and document a comprehensive alerting strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing alerting strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the alerting strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the alerting strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Alerting Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/api-design/SKILL.md b/clowdex-download/.claude/.claude/skills/development/api-design/SKILL.md new file mode 100644 index 0000000..deda013 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/api-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a api design with structured process, quality checks, and system integration +--- + +# Api Design + +## Purpose + +Create a comprehensive api design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api design +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Api Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/api-documentation-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/development/api-documentation-writer/SKILL.md new file mode 100644 index 0000000..72d032c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/api-documentation-writer/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a api documentation writer with structured process, quality checks, and system integration +--- + +# Api Documentation Writer + +## Purpose + +Create a comprehensive api documentation writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api documentation writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api documentation writer +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api documentation writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Api Documentation Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/api-gateway-design/SKILL.md b/clowdex-download/.claude/.claude/skills/development/api-gateway-design/SKILL.md new file mode 100644 index 0000000..05fe93b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/api-gateway-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a api gateway design with structured process, quality checks, and system integration +--- + +# Api Gateway Design + +## Purpose + +Create a comprehensive api gateway design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api gateway design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api gateway design +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api gateway design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Api Gateway Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/api-versioning-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/api-versioning-strategy/SKILL.md new file mode 100644 index 0000000..3e6539a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/api-versioning-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a api versioning strategy with structured process, quality checks, and system integration +--- + +# Api Versioning Strategy + +## Purpose + +Design and document a comprehensive api versioning strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api versioning strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api versioning strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api versioning strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Api Versioning Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/architecture-decision-record/SKILL.md b/clowdex-download/.claude/.claude/skills/development/architecture-decision-record/SKILL.md new file mode 100644 index 0000000..f606972 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/architecture-decision-record/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a architecture decision record with structured process, quality checks, and system integration +--- + +# Architecture Decision Record + +## Purpose + +Create a comprehensive architecture decision record that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing architecture decision record documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the architecture decision record +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the architecture decision record using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Architecture Decision Record + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/architecture-overview/SKILL.md b/clowdex-download/.claude/.claude/skills/development/architecture-overview/SKILL.md new file mode 100644 index 0000000..07dfe28 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/architecture-overview/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a architecture overview with structured process, quality checks, and system integration +--- + +# Architecture Overview + +## Purpose + +Create a comprehensive architecture overview that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing architecture overview documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the architecture overview +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the architecture overview using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Architecture Overview + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/blue-green-deployment/SKILL.md b/clowdex-download/.claude/.claude/skills/development/blue-green-deployment/SKILL.md new file mode 100644 index 0000000..370fb61 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/blue-green-deployment/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a blue green deployment with structured process, quality checks, and system integration +--- + +# Blue Green Deployment + +## Purpose + +Create a comprehensive blue green deployment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing blue green deployment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the blue green deployment +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the blue green deployment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Blue Green Deployment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/branching-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/branching-strategy/SKILL.md new file mode 100644 index 0000000..405f183 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/branching-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a branching strategy with structured process, quality checks, and system integration +--- + +# Branching Strategy + +## Purpose + +Design and document a comprehensive branching strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing branching strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the branching strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the branching strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Branching Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/caching-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/caching-strategy/SKILL.md new file mode 100644 index 0000000..923b6c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/caching-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a caching strategy with structured process, quality checks, and system integration +--- + +# Caching Strategy + +## Purpose + +Design and document a comprehensive caching strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing caching strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the caching strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the caching strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Caching Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/canary-deployment/SKILL.md b/clowdex-download/.claude/.claude/skills/development/canary-deployment/SKILL.md new file mode 100644 index 0000000..9abc5bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/canary-deployment/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a canary deployment with structured process, quality checks, and system integration +--- + +# Canary Deployment + +## Purpose + +Create a comprehensive canary deployment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing canary deployment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the canary deployment +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the canary deployment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Canary Deployment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/ci-cd-pipeline/SKILL.md b/clowdex-download/.claude/.claude/skills/development/ci-cd-pipeline/SKILL.md new file mode 100644 index 0000000..dd32741 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/ci-cd-pipeline/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a ci cd pipeline with structured process, quality checks, and system integration +--- + +# Ci Cd Pipeline + +## Purpose + +Design and document a comprehensive ci cd pipeline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ci cd pipeline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ci cd pipeline +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ci cd pipeline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Ci Cd Pipeline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/circuit-breaker-pattern/SKILL.md b/clowdex-download/.claude/.claude/skills/development/circuit-breaker-pattern/SKILL.md new file mode 100644 index 0000000..875d14f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/circuit-breaker-pattern/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a circuit breaker pattern with structured process, quality checks, and system integration +--- + +# Circuit Breaker Pattern + +## Purpose + +Create a comprehensive circuit breaker pattern that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing circuit breaker pattern documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the circuit breaker pattern +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the circuit breaker pattern using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Circuit Breaker Pattern + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/code-cleanup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/code-cleanup/SKILL.md new file mode 100644 index 0000000..5677b2b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/code-cleanup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a code cleanup with structured process, quality checks, and system integration +--- + +# Code Cleanup + +## Purpose + +Create a comprehensive code cleanup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing code cleanup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the code cleanup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the code cleanup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Code Cleanup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/code-review-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/code-review-checklist/SKILL.md new file mode 100644 index 0000000..cfe8ffe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/code-review-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a code review checklist with structured process, quality checks, and system integration +--- + +# Code Review Checklist + +## Purpose + +Analyze and produce a comprehensive code review checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing code review checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the code review checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the code review checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Code Review Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/codebase-walkthrough/SKILL.md b/clowdex-download/.claude/.claude/skills/development/codebase-walkthrough/SKILL.md new file mode 100644 index 0000000..44d2a5a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/codebase-walkthrough/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a codebase walkthrough with structured process, quality checks, and system integration +--- + +# Codebase Walkthrough + +## Purpose + +Create a comprehensive codebase walkthrough that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing codebase walkthrough documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the codebase walkthrough +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the codebase walkthrough using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Codebase Walkthrough + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/coding-standards/SKILL.md b/clowdex-download/.claude/.claude/skills/development/coding-standards/SKILL.md new file mode 100644 index 0000000..329145e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/coding-standards/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a coding standards with structured process, quality checks, and system integration +--- + +# Coding Standards + +## Purpose + +Create a comprehensive coding standards that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing coding standards documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the coding standards +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the coding standards using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Coding Standards + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/commit-message-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/development/commit-message-guide/SKILL.md new file mode 100644 index 0000000..5df9a5a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/commit-message-guide/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a commit message guide with structured process, quality checks, and system integration +--- + +# Commit Message Guide + +## Purpose + +Design and document a comprehensive commit message guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing commit message guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the commit message guide +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the commit message guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Commit Message Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/contributing-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/development/contributing-guide/SKILL.md new file mode 100644 index 0000000..4cc3c37 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/contributing-guide/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a contributing guide with structured process, quality checks, and system integration +--- + +# Contributing Guide + +## Purpose + +Design and document a comprehensive contributing guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing contributing guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the contributing guide +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the contributing guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Contributing Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/cross-browser-testing/SKILL.md b/clowdex-download/.claude/.claude/skills/development/cross-browser-testing/SKILL.md new file mode 100644 index 0000000..ce092e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/cross-browser-testing/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a cross browser testing with structured process, quality checks, and system integration +--- + +# Cross Browser Testing + +## Purpose + +Create a comprehensive cross browser testing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross browser testing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross browser testing +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross browser testing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Cross Browser Testing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/data-model-documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/development/data-model-documentation/SKILL.md new file mode 100644 index 0000000..d5dab42 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/data-model-documentation/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a data model documentation with structured process, quality checks, and system integration +--- + +# Data Model Documentation + +## Purpose + +Design and document a comprehensive data model documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data model documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data model documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data model documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Data Model Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/database-schema-design/SKILL.md b/clowdex-download/.claude/.claude/skills/development/database-schema-design/SKILL.md new file mode 100644 index 0000000..68ca5c5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/database-schema-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a database schema design with structured process, quality checks, and system integration +--- + +# Database Schema Design + +## Purpose + +Create a comprehensive database schema design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing database schema design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the database schema design +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the database schema design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Database Schema Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/dependency-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/development/dependency-audit/SKILL.md new file mode 100644 index 0000000..4646be5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/dependency-audit/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a dependency audit with structured process, quality checks, and system integration +--- + +# Dependency Audit + +## Purpose + +Analyze and produce a comprehensive dependency audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dependency audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dependency audit +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dependency audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Dependency Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/deployment-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/deployment-checklist/SKILL.md new file mode 100644 index 0000000..51872ee --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/deployment-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a deployment checklist with structured process, quality checks, and system integration +--- + +# Deployment Checklist + +## Purpose + +Analyze and produce a comprehensive deployment checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deployment checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deployment checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deployment checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Deployment Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/dev-environment-parity/SKILL.md b/clowdex-download/.claude/.claude/skills/development/dev-environment-parity/SKILL.md new file mode 100644 index 0000000..443528a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/dev-environment-parity/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a dev environment parity with structured process, quality checks, and system integration +--- + +# Dev Environment Parity + +## Purpose + +Create a comprehensive dev environment parity that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dev environment parity documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dev environment parity +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dev environment parity using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Dev Environment Parity + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/developer-onboarding/SKILL.md b/clowdex-download/.claude/.claude/skills/development/developer-onboarding/SKILL.md new file mode 100644 index 0000000..f3c9f6a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/developer-onboarding/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a developer onboarding with structured process, quality checks, and system integration +--- + +# Developer Onboarding + +## Purpose + +Create a comprehensive developer onboarding that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing developer onboarding documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the developer onboarding +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the developer onboarding using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Developer Onboarding + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/distributed-tracing/SKILL.md b/clowdex-download/.claude/.claude/skills/development/distributed-tracing/SKILL.md new file mode 100644 index 0000000..de51226 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/distributed-tracing/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a distributed tracing with structured process, quality checks, and system integration +--- + +# Distributed Tracing + +## Purpose + +Create a comprehensive distributed tracing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing distributed tracing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the distributed tracing +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the distributed tracing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Distributed Tracing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/docker-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/docker-setup/SKILL.md new file mode 100644 index 0000000..3ef7134 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/docker-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a docker setup with structured process, quality checks, and system integration +--- + +# Docker Setup + +## Purpose + +Design and document a comprehensive docker setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing docker setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the docker setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the docker setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Docker Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/documentation-standard/SKILL.md b/clowdex-download/.claude/.claude/skills/development/documentation-standard/SKILL.md new file mode 100644 index 0000000..59bd4dc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/documentation-standard/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a documentation standard with structured process, quality checks, and system integration +--- + +# Documentation Standard + +## Purpose + +Create a comprehensive documentation standard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing documentation standard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the documentation standard +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the documentation standard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Documentation Standard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/e2e-test-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/e2e-test-strategy/SKILL.md new file mode 100644 index 0000000..5f51fca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/e2e-test-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a e2e test strategy with structured process, quality checks, and system integration +--- + +# E2e Test Strategy + +## Purpose + +Design and document a comprehensive e2e test strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing e2e test strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the e2e test strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the e2e test strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# E2e Test Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/environment-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/environment-setup/SKILL.md new file mode 100644 index 0000000..e5a8001 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/environment-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a environment setup with structured process, quality checks, and system integration +--- + +# Environment Setup + +## Purpose + +Design and document a comprehensive environment setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing environment setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the environment setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the environment setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Environment Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/error-handling-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/development/error-handling-guide/SKILL.md new file mode 100644 index 0000000..ffd796b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/error-handling-guide/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a error handling guide with structured process, quality checks, and system integration +--- + +# Error Handling Guide + +## Purpose + +Design and document a comprehensive error handling guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing error handling guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the error handling guide +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the error handling guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Error Handling Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/event-driven-architecture/SKILL.md b/clowdex-download/.claude/.claude/skills/development/event-driven-architecture/SKILL.md new file mode 100644 index 0000000..ea53902 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/event-driven-architecture/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a event driven architecture with structured process, quality checks, and system integration +--- + +# Event Driven Architecture + +## Purpose + +Create a comprehensive event driven architecture that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event driven architecture documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event driven architecture +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event driven architecture using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Event Driven Architecture + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/feature-flag-implementation/SKILL.md b/clowdex-download/.claude/.claude/skills/development/feature-flag-implementation/SKILL.md new file mode 100644 index 0000000..47e1adf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/feature-flag-implementation/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a feature flag implementation with structured process, quality checks, and system integration +--- + +# Feature Flag Implementation + +## Purpose + +Create a comprehensive feature flag implementation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature flag implementation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature flag implementation +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature flag implementation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Feature Flag Implementation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/git-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/development/git-workflow/SKILL.md new file mode 100644 index 0000000..555c3a0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/git-workflow/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a git workflow with structured process, quality checks, and system integration +--- + +# Git Workflow + +## Purpose + +Design and document a comprehensive git workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing git workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the git workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the git workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Git Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/incident-response/SKILL.md b/clowdex-download/.claude/.claude/skills/development/incident-response/SKILL.md new file mode 100644 index 0000000..dcf781a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/incident-response/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a incident response with structured process, quality checks, and system integration +--- + +# Incident Response + +## Purpose + +Create a comprehensive incident response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident response +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Incident Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/infrastructure-as-code/SKILL.md b/clowdex-download/.claude/.claude/skills/development/infrastructure-as-code/SKILL.md new file mode 100644 index 0000000..090f67a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/infrastructure-as-code/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a infrastructure as code with structured process, quality checks, and system integration +--- + +# Infrastructure As Code + +## Purpose + +Create a comprehensive infrastructure as code that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing infrastructure as code documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the infrastructure as code +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the infrastructure as code using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Infrastructure As Code + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/integration-test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/development/integration-test-plan/SKILL.md new file mode 100644 index 0000000..a753026 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/integration-test-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a integration test plan with structured process, quality checks, and system integration +--- + +# Integration Test Plan + +## Purpose + +Design and document a comprehensive integration test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing integration test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the integration test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the integration test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Integration Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/kubernetes-deployment/SKILL.md b/clowdex-download/.claude/.claude/skills/development/kubernetes-deployment/SKILL.md new file mode 100644 index 0000000..5ebce46 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/kubernetes-deployment/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a kubernetes deployment with structured process, quality checks, and system integration +--- + +# Kubernetes Deployment + +## Purpose + +Create a comprehensive kubernetes deployment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kubernetes deployment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kubernetes deployment +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kubernetes deployment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Kubernetes Deployment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/license-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/development/license-compliance/SKILL.md new file mode 100644 index 0000000..49d643f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/license-compliance/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a license compliance with structured process, quality checks, and system integration +--- + +# License Compliance + +## Purpose + +Create a comprehensive license compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing license compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the license compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the license compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# License Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/linting-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/linting-setup/SKILL.md new file mode 100644 index 0000000..5f420d3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/linting-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a linting setup with structured process, quality checks, and system integration +--- + +# Linting Setup + +## Purpose + +Design and document a comprehensive linting setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linting setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linting setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linting setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Linting Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/load-test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/development/load-test-plan/SKILL.md new file mode 100644 index 0000000..8825207 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/load-test-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a load test plan with structured process, quality checks, and system integration +--- + +# Load Test Plan + +## Purpose + +Design and document a comprehensive load test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing load test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the load test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the load test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Load Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/local-dev-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/local-dev-setup/SKILL.md new file mode 100644 index 0000000..31f057f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/local-dev-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a local dev setup with structured process, quality checks, and system integration +--- + +# Local Dev Setup + +## Purpose + +Design and document a comprehensive local dev setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local dev setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local dev setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local dev setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Local Dev Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/logging-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/logging-strategy/SKILL.md new file mode 100644 index 0000000..8960125 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/logging-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a logging strategy with structured process, quality checks, and system integration +--- + +# Logging Strategy + +## Purpose + +Design and document a comprehensive logging strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing logging strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the logging strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the logging strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Logging Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/microservices-design/SKILL.md b/clowdex-download/.claude/.claude/skills/development/microservices-design/SKILL.md new file mode 100644 index 0000000..75b9498 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/microservices-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a microservices design with structured process, quality checks, and system integration +--- + +# Microservices Design + +## Purpose + +Create a comprehensive microservices design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing microservices design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the microservices design +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the microservices design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Microservices Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/migration-script/SKILL.md b/clowdex-download/.claude/.claude/skills/development/migration-script/SKILL.md new file mode 100644 index 0000000..7cf7fe7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/migration-script/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a migration script with structured process, quality checks, and system integration +--- + +# Migration Script + +## Purpose + +Create a comprehensive migration script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing migration script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the migration script +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the migration script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Migration Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/monitoring-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/monitoring-setup/SKILL.md new file mode 100644 index 0000000..71545ee --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/monitoring-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a monitoring setup with structured process, quality checks, and system integration +--- + +# Monitoring Setup + +## Purpose + +Analyze and produce a comprehensive monitoring setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing monitoring setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the monitoring setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the monitoring setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Monitoring Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/observability-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/development/observability-setup/SKILL.md new file mode 100644 index 0000000..394ab23 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/observability-setup/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a observability setup with structured process, quality checks, and system integration +--- + +# Observability Setup + +## Purpose + +Design and document a comprehensive observability setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing observability setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the observability setup +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the observability setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Observability Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/on-call-runbook/SKILL.md b/clowdex-download/.claude/.claude/skills/development/on-call-runbook/SKILL.md new file mode 100644 index 0000000..65417d5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/on-call-runbook/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a on call runbook with structured process, quality checks, and system integration +--- + +# On Call Runbook + +## Purpose + +Create a comprehensive on call runbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing on call runbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the on call runbook +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the on call runbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# On Call Runbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/open-source-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/open-source-checklist/SKILL.md new file mode 100644 index 0000000..de9ccce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/open-source-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a open source checklist with structured process, quality checks, and system integration +--- + +# Open Source Checklist + +## Purpose + +Analyze and produce a comprehensive open source checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing open source checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the open source checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the open source checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Open Source Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/optimization-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/optimization-checklist/SKILL.md new file mode 100644 index 0000000..0cfb35f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/optimization-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a optimization checklist with structured process, quality checks, and system integration +--- + +# Optimization Checklist + +## Purpose + +Analyze and produce a comprehensive optimization checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing optimization checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the optimization checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the optimization checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Optimization Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/package-publishing/SKILL.md b/clowdex-download/.claude/.claude/skills/development/package-publishing/SKILL.md new file mode 100644 index 0000000..66e922b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/package-publishing/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a package publishing with structured process, quality checks, and system integration +--- + +# Package Publishing + +## Purpose + +Create a comprehensive package publishing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing package publishing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the package publishing +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the package publishing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Package Publishing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/performance-profiling/SKILL.md b/clowdex-download/.claude/.claude/skills/development/performance-profiling/SKILL.md new file mode 100644 index 0000000..3797505 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/performance-profiling/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a performance profiling with structured process, quality checks, and system integration +--- + +# Performance Profiling + +## Purpose + +Analyze and produce a comprehensive performance profiling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing performance profiling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the performance profiling +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the performance profiling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Performance Profiling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/postmortem-template/SKILL.md b/clowdex-download/.claude/.claude/skills/development/postmortem-template/SKILL.md new file mode 100644 index 0000000..7932318 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/postmortem-template/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a postmortem template with structured process, quality checks, and system integration +--- + +# Postmortem Template + +## Purpose + +Create a comprehensive postmortem template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing postmortem template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the postmortem template +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the postmortem template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Postmortem Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/pre-commit-hooks/SKILL.md b/clowdex-download/.claude/.claude/skills/development/pre-commit-hooks/SKILL.md new file mode 100644 index 0000000..06a0e10 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/pre-commit-hooks/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a pre commit hooks with structured process, quality checks, and system integration +--- + +# Pre Commit Hooks + +## Purpose + +Create a comprehensive pre commit hooks that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pre commit hooks documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pre commit hooks +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pre commit hooks using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Pre Commit Hooks + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/pull-request-template/SKILL.md b/clowdex-download/.claude/.claude/skills/development/pull-request-template/SKILL.md new file mode 100644 index 0000000..06901f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/pull-request-template/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a pull request template with structured process, quality checks, and system integration +--- + +# Pull Request Template + +## Purpose + +Create a comprehensive pull request template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pull request template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pull request template +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pull request template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Pull Request Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/queue-design/SKILL.md b/clowdex-download/.claude/.claude/skills/development/queue-design/SKILL.md new file mode 100644 index 0000000..fd52fd2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/queue-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a queue design with structured process, quality checks, and system integration +--- + +# Queue Design + +## Purpose + +Create a comprehensive queue design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing queue design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the queue design +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the queue design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Queue Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/readme-template/SKILL.md b/clowdex-download/.claude/.claude/skills/development/readme-template/SKILL.md new file mode 100644 index 0000000..f9f2229 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/readme-template/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a readme template with structured process, quality checks, and system integration +--- + +# Readme Template + +## Purpose + +Create a comprehensive readme template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing readme template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the readme template +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the readme template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Readme Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/refactoring-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/development/refactoring-plan/SKILL.md new file mode 100644 index 0000000..0205d46 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/refactoring-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a refactoring plan with structured process, quality checks, and system integration +--- + +# Refactoring Plan + +## Purpose + +Design and document a comprehensive refactoring plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing refactoring plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the refactoring plan +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the refactoring plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Refactoring Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/release-management/SKILL.md b/clowdex-download/.claude/.claude/skills/development/release-management/SKILL.md new file mode 100644 index 0000000..50e5696 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/release-management/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a release management with structured process, quality checks, and system integration +--- + +# Release Management + +## Purpose + +Create a comprehensive release management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing release management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the release management +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the release management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Release Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/responsive-design-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/responsive-design-checklist/SKILL.md new file mode 100644 index 0000000..dae290e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/responsive-design-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a responsive design checklist with structured process, quality checks, and system integration +--- + +# Responsive Design Checklist + +## Purpose + +Analyze and produce a comprehensive responsive design checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing responsive design checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the responsive design checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the responsive design checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Responsive Design Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/retry-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/development/retry-strategy/SKILL.md new file mode 100644 index 0000000..b8deea1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/retry-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a retry strategy with structured process, quality checks, and system integration +--- + +# Retry Strategy + +## Purpose + +Design and document a comprehensive retry strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retry strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retry strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retry strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Retry Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/rollback-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/development/rollback-plan/SKILL.md new file mode 100644 index 0000000..baa67ab --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/rollback-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a rollback plan with structured process, quality checks, and system integration +--- + +# Rollback Plan + +## Purpose + +Design and document a comprehensive rollback plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rollback plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rollback plan +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rollback plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Rollback Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/root-cause-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/development/root-cause-analysis/SKILL.md new file mode 100644 index 0000000..01e5690 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/root-cause-analysis/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a root cause analysis with structured process, quality checks, and system integration +--- + +# Root Cause Analysis + +## Purpose + +Analyze and produce a comprehensive root cause analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing root cause analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the root cause analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the root cause analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Root Cause Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/security-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/development/security-checklist/SKILL.md new file mode 100644 index 0000000..eaee7a3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/security-checklist/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a security checklist with structured process, quality checks, and system integration +--- + +# Security Checklist + +## Purpose + +Analyze and produce a comprehensive security checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing security checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the security checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the security checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Security Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/security-review/SKILL.md b/clowdex-download/.claude/.claude/skills/development/security-review/SKILL.md new file mode 100644 index 0000000..1661894 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/security-review/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a security review with structured process, quality checks, and system integration +--- + +# Security Review + +## Purpose + +Analyze and produce a comprehensive security review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing security review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the security review +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the security review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Security Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/semantic-versioning/SKILL.md b/clowdex-download/.claude/.claude/skills/development/semantic-versioning/SKILL.md new file mode 100644 index 0000000..63f1265 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/semantic-versioning/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a semantic versioning with structured process, quality checks, and system integration +--- + +# Semantic Versioning + +## Purpose + +Create a comprehensive semantic versioning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing semantic versioning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the semantic versioning +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the semantic versioning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Semantic Versioning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/service-boundary/SKILL.md b/clowdex-download/.claude/.claude/skills/development/service-boundary/SKILL.md new file mode 100644 index 0000000..06ddf5b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/service-boundary/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a service boundary with structured process, quality checks, and system integration +--- + +# Service Boundary + +## Purpose + +Create a comprehensive service boundary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing service boundary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the service boundary +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the service boundary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Service Boundary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/supply-chain-security/SKILL.md b/clowdex-download/.claude/.claude/skills/development/supply-chain-security/SKILL.md new file mode 100644 index 0000000..a7a5ed3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/supply-chain-security/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a supply chain security with structured process, quality checks, and system integration +--- + +# Supply Chain Security + +## Purpose + +Create a comprehensive supply chain security that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing supply chain security documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the supply chain security +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the supply chain security using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Supply Chain Security + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/system-design-doc/SKILL.md b/clowdex-download/.claude/.claude/skills/development/system-design-doc/SKILL.md new file mode 100644 index 0000000..5bcfd61 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/system-design-doc/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a system design doc with structured process, quality checks, and system integration +--- + +# System Design Doc + +## Purpose + +Create a comprehensive system design doc that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing system design doc documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the system design doc +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the system design doc using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# System Design Doc + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/tech-debt-inventory/SKILL.md b/clowdex-download/.claude/.claude/skills/development/tech-debt-inventory/SKILL.md new file mode 100644 index 0000000..b304454 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/tech-debt-inventory/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a tech debt inventory with structured process, quality checks, and system integration +--- + +# Tech Debt Inventory + +## Purpose + +Create a comprehensive tech debt inventory that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tech debt inventory documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tech debt inventory +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tech debt inventory using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Tech Debt Inventory + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/technical-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/development/technical-spec/SKILL.md new file mode 100644 index 0000000..353d841 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/technical-spec/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a technical spec with structured process, quality checks, and system integration +--- + +# Technical Spec + +## Purpose + +Create a comprehensive technical spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technical spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technical spec +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technical spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Technical Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/test-coverage-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/development/test-coverage-analysis/SKILL.md new file mode 100644 index 0000000..9733369 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/test-coverage-analysis/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a test coverage analysis with structured process, quality checks, and system integration +--- + +# Test Coverage Analysis + +## Purpose + +Analyze and produce a comprehensive test coverage analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing test coverage analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the test coverage analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the test coverage analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Test Coverage Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/development/test-plan/SKILL.md new file mode 100644 index 0000000..1da0f21 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/test-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a test plan with structured process, quality checks, and system integration +--- + +# Test Plan + +## Purpose + +Design and document a comprehensive test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/testing-pyramid/SKILL.md b/clowdex-download/.claude/.claude/skills/development/testing-pyramid/SKILL.md new file mode 100644 index 0000000..9ed96ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/testing-pyramid/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a testing pyramid with structured process, quality checks, and system integration +--- + +# Testing Pyramid + +## Purpose + +Create a comprehensive testing pyramid that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing testing pyramid documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the testing pyramid +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the testing pyramid using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Testing Pyramid + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/unit-test-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/development/unit-test-writer/SKILL.md new file mode 100644 index 0000000..1f51bcd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/unit-test-writer/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a unit test writer with structured process, quality checks, and system integration +--- + +# Unit Test Writer + +## Purpose + +Create a comprehensive unit test writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing unit test writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the unit test writer +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the unit test writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Unit Test Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/development/vulnerability-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/development/vulnerability-assessment/SKILL.md new file mode 100644 index 0000000..db544a5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/development/vulnerability-assessment/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a vulnerability assessment with structured process, quality checks, and system integration +--- + +# Vulnerability Assessment + +## Purpose + +Analyze and produce a comprehensive vulnerability assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Software Development + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Codebase Context**: Language, framework, and architecture + +### Optional +- **Constraints**: Performance requirements, compatibility needs +- **Team Standards**: Existing coding conventions or style guides + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vulnerability assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Clean Architecture, SOLID Principles, TDD/BDD + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vulnerability assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Mean Time to Recovery (MTTR) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vulnerability assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Code reviews within 24 hours + +## Output Format + +```markdown +# Vulnerability Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Clean Architecture +- SOLID Principles +- TDD/BDD +- 12-Factor App +- GitFlow/Trunk-Based Development +- Microservices vs Monolith decision tree +- OWASP Top 10 + +## Key Metrics +- Deployment Frequency +- Lead Time for Changes +- Change Failure Rate +- Mean Time to Recovery (MTTR) +- Code Coverage +- Cyclomatic Complexity +- Technical Debt Ratio + +## Best Practices +- Code reviews within 24 hours +- Every PR should be reviewable in under 30 minutes +- Write tests before fixing bugs +- Automate everything that runs more than twice +- Document decisions, not just code + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/amazon-listing/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/amazon-listing/SKILL.md new file mode 100644 index 0000000..151d767 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/amazon-listing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a amazon listing with structured process, quality checks, and system integration +--- + +# Amazon Listing + +## Purpose + +Create a comprehensive amazon listing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing amazon listing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the amazon listing +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the amazon listing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Amazon Listing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/amazon-ppc-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/amazon-ppc-strategy/SKILL.md new file mode 100644 index 0000000..b0a9e6c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/amazon-ppc-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a amazon ppc strategy with structured process, quality checks, and system integration +--- + +# Amazon Ppc Strategy + +## Purpose + +Design and document a comprehensive amazon ppc strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing amazon ppc strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the amazon ppc strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the amazon ppc strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Amazon Ppc Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/black-friday-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/black-friday-strategy/SKILL.md new file mode 100644 index 0000000..311a1f9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/black-friday-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a black friday strategy with structured process, quality checks, and system integration +--- + +# Black Friday Strategy + +## Purpose + +Design and document a comprehensive black friday strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing black friday strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the black friday strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the black friday strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Black Friday Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/bundle-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/bundle-strategy/SKILL.md new file mode 100644 index 0000000..314d92f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/bundle-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a bundle strategy with structured process, quality checks, and system integration +--- + +# Bundle Strategy + +## Purpose + +Design and document a comprehensive bundle strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bundle strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bundle strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bundle strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Bundle Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/cart-abandonment-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/cart-abandonment-analysis/SKILL.md new file mode 100644 index 0000000..97938e2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/cart-abandonment-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a cart abandonment analysis with structured process, quality checks, and system integration +--- + +# Cart Abandonment Analysis + +## Purpose + +Analyze and produce a comprehensive cart abandonment analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cart abandonment analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cart abandonment analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cart abandonment analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Cart Abandonment Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/category-taxonomy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/category-taxonomy/SKILL.md new file mode 100644 index 0000000..d851e24 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/category-taxonomy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a category taxonomy with structured process, quality checks, and system integration +--- + +# Category Taxonomy + +## Purpose + +Create a comprehensive category taxonomy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing category taxonomy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the category taxonomy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the category taxonomy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Category Taxonomy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/checkout-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/checkout-optimization/SKILL.md new file mode 100644 index 0000000..d859412 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/checkout-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a checkout optimization with structured process, quality checks, and system integration +--- + +# Checkout Optimization + +## Purpose + +Analyze and produce a comprehensive checkout optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing checkout optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the checkout optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the checkout optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Checkout Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/collection-page-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/collection-page-design/SKILL.md new file mode 100644 index 0000000..2855027 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/collection-page-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a collection page design with structured process, quality checks, and system integration +--- + +# Collection Page Design + +## Purpose + +Create a comprehensive collection page design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing collection page design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the collection page design +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the collection page design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Collection Page Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/conversion-rate-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/conversion-rate-audit/SKILL.md new file mode 100644 index 0000000..6c8ac96 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/conversion-rate-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a conversion rate audit with structured process, quality checks, and system integration +--- + +# Conversion Rate Audit + +## Purpose + +Analyze and produce a comprehensive conversion rate audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conversion rate audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conversion rate audit +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conversion rate audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Conversion Rate Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/cross-border-ecommerce/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/cross-border-ecommerce/SKILL.md new file mode 100644 index 0000000..9cd8922 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/cross-border-ecommerce/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cross border ecommerce with structured process, quality checks, and system integration +--- + +# Cross Border Ecommerce + +## Purpose + +Create a comprehensive cross border ecommerce that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross border ecommerce documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross border ecommerce +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross border ecommerce using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Cross Border Ecommerce + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/customer-acquisition-cost/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/customer-acquisition-cost/SKILL.md new file mode 100644 index 0000000..1a2e61d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/customer-acquisition-cost/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer acquisition cost with structured process, quality checks, and system integration +--- + +# Customer Acquisition Cost + +## Purpose + +Create a comprehensive customer acquisition cost that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer acquisition cost documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer acquisition cost +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer acquisition cost using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Customer Acquisition Cost + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/customer-lifetime-value/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/customer-lifetime-value/SKILL.md new file mode 100644 index 0000000..898b2cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/customer-lifetime-value/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer lifetime value with structured process, quality checks, and system integration +--- + +# Customer Lifetime Value + +## Purpose + +Create a comprehensive customer lifetime value that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer lifetime value documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer lifetime value +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer lifetime value using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Customer Lifetime Value + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/customer-review-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/customer-review-strategy/SKILL.md new file mode 100644 index 0000000..e0c62bc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/customer-review-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a customer review strategy with structured process, quality checks, and system integration +--- + +# Customer Review Strategy + +## Purpose + +Analyze and produce a comprehensive customer review strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer review strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer review strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer review strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Customer Review Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/customer-segmentation-ecom/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/customer-segmentation-ecom/SKILL.md new file mode 100644 index 0000000..195a613 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/customer-segmentation-ecom/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer segmentation ecom with structured process, quality checks, and system integration +--- + +# Customer Segmentation Ecom + +## Purpose + +Create a comprehensive customer segmentation ecom that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer segmentation ecom documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer segmentation ecom +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer segmentation ecom using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Customer Segmentation Ecom + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/dead-stock-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/dead-stock-analysis/SKILL.md new file mode 100644 index 0000000..8bbcf29 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/dead-stock-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a dead stock analysis with structured process, quality checks, and system integration +--- + +# Dead Stock Analysis + +## Purpose + +Analyze and produce a comprehensive dead stock analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dead stock analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dead stock analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dead stock analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Dead Stock Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/dropshipping-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/dropshipping-setup/SKILL.md new file mode 100644 index 0000000..86db720 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/dropshipping-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a dropshipping setup with structured process, quality checks, and system integration +--- + +# Dropshipping Setup + +## Purpose + +Design and document a comprehensive dropshipping setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dropshipping setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dropshipping setup +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dropshipping setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Dropshipping Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/dynamic-pricing-model/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/dynamic-pricing-model/SKILL.md new file mode 100644 index 0000000..5234d87 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/dynamic-pricing-model/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a dynamic pricing model with structured process, quality checks, and system integration +--- + +# Dynamic Pricing Model + +## Purpose + +Design and document a comprehensive dynamic pricing model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dynamic pricing model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dynamic pricing model +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dynamic pricing model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Dynamic Pricing Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/ecommerce-analytics/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/ecommerce-analytics/SKILL.md new file mode 100644 index 0000000..4016b09 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/ecommerce-analytics/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ecommerce analytics with structured process, quality checks, and system integration +--- + +# Ecommerce Analytics + +## Purpose + +Create a comprehensive ecommerce analytics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ecommerce analytics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ecommerce analytics +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ecommerce analytics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Ecommerce Analytics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/email-marketing-ecom/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/email-marketing-ecom/SKILL.md new file mode 100644 index 0000000..d0a7004 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/email-marketing-ecom/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a email marketing ecom with structured process, quality checks, and system integration +--- + +# Email Marketing Ecom + +## Purpose + +Create a comprehensive email marketing ecom that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email marketing ecom documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email marketing ecom +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email marketing ecom using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Email Marketing Ecom + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/etsy-listing/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/etsy-listing/SKILL.md new file mode 100644 index 0000000..2dd9af5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/etsy-listing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a etsy listing with structured process, quality checks, and system integration +--- + +# Etsy Listing + +## Purpose + +Create a comprehensive etsy listing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing etsy listing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the etsy listing +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the etsy listing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Etsy Listing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/flash-sale-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/flash-sale-plan/SKILL.md new file mode 100644 index 0000000..4f63f1a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/flash-sale-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a flash sale plan with structured process, quality checks, and system integration +--- + +# Flash Sale Plan + +## Purpose + +Design and document a comprehensive flash sale plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing flash sale plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the flash sale plan +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the flash sale plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Flash Sale Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/fulfillment-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/fulfillment-optimization/SKILL.md new file mode 100644 index 0000000..0e59e47 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/fulfillment-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a fulfillment optimization with structured process, quality checks, and system integration +--- + +# Fulfillment Optimization + +## Purpose + +Create a comprehensive fulfillment optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fulfillment optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fulfillment optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fulfillment optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Fulfillment Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/inventory-forecasting/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/inventory-forecasting/SKILL.md new file mode 100644 index 0000000..5455332 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/inventory-forecasting/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a inventory forecasting with structured process, quality checks, and system integration +--- + +# Inventory Forecasting + +## Purpose + +Analyze and produce a comprehensive inventory forecasting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inventory forecasting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inventory forecasting +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inventory forecasting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Inventory Forecasting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/landing-page-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/landing-page-optimization/SKILL.md new file mode 100644 index 0000000..c25dd92 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/landing-page-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a landing page optimization with structured process, quality checks, and system integration +--- + +# Landing Page Optimization + +## Purpose + +Create a comprehensive landing page optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing landing page optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the landing page optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the landing page optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Landing Page Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/localization-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/localization-checklist/SKILL.md new file mode 100644 index 0000000..8ec9deb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/localization-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a localization checklist with structured process, quality checks, and system integration +--- + +# Localization Checklist + +## Purpose + +Analyze and produce a comprehensive localization checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing localization checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the localization checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the localization checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Localization Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/loyalty-program-design/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/loyalty-program-design/SKILL.md new file mode 100644 index 0000000..c80c0f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/loyalty-program-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a loyalty program design with structured process, quality checks, and system integration +--- + +# Loyalty Program Design + +## Purpose + +Create a comprehensive loyalty program design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing loyalty program design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the loyalty program design +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the loyalty program design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Loyalty Program Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/marketplace-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/marketplace-strategy/SKILL.md new file mode 100644 index 0000000..fabc06a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/marketplace-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a marketplace strategy with structured process, quality checks, and system integration +--- + +# Marketplace Strategy + +## Purpose + +Design and document a comprehensive marketplace strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketplace strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketplace strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketplace strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Marketplace Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/multi-currency-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/multi-currency-strategy/SKILL.md new file mode 100644 index 0000000..7e6b4ef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/multi-currency-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a multi currency strategy with structured process, quality checks, and system integration +--- + +# Multi Currency Strategy + +## Purpose + +Design and document a comprehensive multi currency strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing multi currency strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the multi currency strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the multi currency strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Multi Currency Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/personalization-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/personalization-strategy/SKILL.md new file mode 100644 index 0000000..e956308 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/personalization-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a personalization strategy with structured process, quality checks, and system integration +--- + +# Personalization Strategy + +## Purpose + +Design and document a comprehensive personalization strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing personalization strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the personalization strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the personalization strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Personalization Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/pricing-strategy-ecom/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/pricing-strategy-ecom/SKILL.md new file mode 100644 index 0000000..ee22561 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/pricing-strategy-ecom/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a pricing strategy ecom with structured process, quality checks, and system integration +--- + +# Pricing Strategy Ecom + +## Purpose + +Design and document a comprehensive pricing strategy ecom that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing strategy ecom documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing strategy ecom +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing strategy ecom using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Pricing Strategy Ecom + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-description-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-description-writer/SKILL.md new file mode 100644 index 0000000..ae642d2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-description-writer/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product description writer with structured process, quality checks, and system integration +--- + +# Product Description Writer + +## Purpose + +Create a comprehensive product description writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product description writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product description writer +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product description writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Description Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-listing/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-listing/SKILL.md new file mode 100644 index 0000000..6c3a493 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-listing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product listing with structured process, quality checks, and system integration +--- + +# Product Listing + +## Purpose + +Create a comprehensive product listing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product listing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product listing +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product listing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Listing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-page-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-page-optimization/SKILL.md new file mode 100644 index 0000000..cec35f5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-page-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product page optimization with structured process, quality checks, and system integration +--- + +# Product Page Optimization + +## Purpose + +Create a comprehensive product page optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product page optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product page optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product page optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Page Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-performance-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-performance-analysis/SKILL.md new file mode 100644 index 0000000..e6cd118 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-performance-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a product performance analysis with structured process, quality checks, and system integration +--- + +# Product Performance Analysis + +## Purpose + +Analyze and produce a comprehensive product performance analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product performance analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product performance analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product performance analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Performance Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-photography-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-photography-brief/SKILL.md new file mode 100644 index 0000000..9882a08 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-photography-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product photography brief with structured process, quality checks, and system integration +--- + +# Product Photography Brief + +## Purpose + +Create a comprehensive product photography brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product photography brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product photography brief +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product photography brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Photography Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-title-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-title-optimization/SKILL.md new file mode 100644 index 0000000..ba98ed4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-title-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product title optimization with structured process, quality checks, and system integration +--- + +# Product Title Optimization + +## Purpose + +Create a comprehensive product title optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product title optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product title optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product title optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Title Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/product-video-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/product-video-brief/SKILL.md new file mode 100644 index 0000000..6fbb46e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/product-video-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product video brief with structured process, quality checks, and system integration +--- + +# Product Video Brief + +## Purpose + +Create a comprehensive product video brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product video brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product video brief +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product video brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Product Video Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/push-notification-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/push-notification-strategy/SKILL.md new file mode 100644 index 0000000..1accbc3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/push-notification-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a push notification strategy with structured process, quality checks, and system integration +--- + +# Push Notification Strategy + +## Purpose + +Design and document a comprehensive push notification strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing push notification strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the push notification strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the push notification strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Push Notification Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/recommendation-engine/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/recommendation-engine/SKILL.md new file mode 100644 index 0000000..9020a76 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/recommendation-engine/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a recommendation engine with structured process, quality checks, and system integration +--- + +# Recommendation Engine + +## Purpose + +Create a comprehensive recommendation engine that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recommendation engine documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recommendation engine +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recommendation engine using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Recommendation Engine + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/returns-policy-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/returns-policy-optimization/SKILL.md new file mode 100644 index 0000000..bb87f81 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/returns-policy-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a returns policy optimization with structured process, quality checks, and system integration +--- + +# Returns Policy Optimization + +## Purpose + +Create a comprehensive returns policy optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing returns policy optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the returns policy optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the returns policy optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Returns Policy Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/review-response-template/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/review-response-template/SKILL.md new file mode 100644 index 0000000..80ad5e5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/review-response-template/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a review response template with structured process, quality checks, and system integration +--- + +# Review Response Template + +## Purpose + +Analyze and produce a comprehensive review response template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review response template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review response template +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review response template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Review Response Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/sales-report/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/sales-report/SKILL.md new file mode 100644 index 0000000..6e78907 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/sales-report/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a sales report with structured process, quality checks, and system integration +--- + +# Sales Report + +## Purpose + +Analyze and produce a comprehensive sales report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales report +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Sales Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/seasonal-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/seasonal-planning/SKILL.md new file mode 100644 index 0000000..9561da3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/seasonal-planning/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a seasonal planning with structured process, quality checks, and system integration +--- + +# Seasonal Planning + +## Purpose + +Design and document a comprehensive seasonal planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seasonal planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seasonal planning +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seasonal planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Seasonal Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/shipping-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/shipping-strategy/SKILL.md new file mode 100644 index 0000000..e93455c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/shipping-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a shipping strategy with structured process, quality checks, and system integration +--- + +# Shipping Strategy + +## Purpose + +Design and document a comprehensive shipping strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing shipping strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the shipping strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the shipping strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Shipping Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/shopify-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/shopify-optimization/SKILL.md new file mode 100644 index 0000000..c25ec71 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/shopify-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a shopify optimization with structured process, quality checks, and system integration +--- + +# Shopify Optimization + +## Purpose + +Create a comprehensive shopify optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing shopify optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the shopify optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the shopify optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Shopify Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/sms-marketing-ecom/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/sms-marketing-ecom/SKILL.md new file mode 100644 index 0000000..b2abd8f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/sms-marketing-ecom/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a sms marketing ecom with structured process, quality checks, and system integration +--- + +# Sms Marketing Ecom + +## Purpose + +Create a comprehensive sms marketing ecom that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sms marketing ecom documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sms marketing ecom +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sms marketing ecom using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Sms Marketing Ecom + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/social-proof-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/social-proof-strategy/SKILL.md new file mode 100644 index 0000000..c950b4d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/social-proof-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a social proof strategy with structured process, quality checks, and system integration +--- + +# Social Proof Strategy + +## Purpose + +Design and document a comprehensive social proof strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social proof strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social proof strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social proof strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Social Proof Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/stock-level-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/stock-level-optimization/SKILL.md new file mode 100644 index 0000000..8abbfb0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/stock-level-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a stock level optimization with structured process, quality checks, and system integration +--- + +# Stock Level Optimization + +## Purpose + +Create a comprehensive stock level optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stock level optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stock level optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stock level optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Stock Level Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/subscription-model/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/subscription-model/SKILL.md new file mode 100644 index 0000000..a6fa11d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/subscription-model/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a subscription model with structured process, quality checks, and system integration +--- + +# Subscription Model + +## Purpose + +Design and document a comprehensive subscription model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subscription model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subscription model +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subscription model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Subscription Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/supplier-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/supplier-evaluation/SKILL.md new file mode 100644 index 0000000..13d77c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/supplier-evaluation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a supplier evaluation with structured process, quality checks, and system integration +--- + +# Supplier Evaluation + +## Purpose + +Analyze and produce a comprehensive supplier evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing supplier evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the supplier evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the supplier evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Supplier Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/unit-economics-ecom/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/unit-economics-ecom/SKILL.md new file mode 100644 index 0000000..9b5a358 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/unit-economics-ecom/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a unit economics ecom with structured process, quality checks, and system integration +--- + +# Unit Economics Ecom + +## Purpose + +Create a comprehensive unit economics ecom that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing unit economics ecom documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the unit economics ecom +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the unit economics ecom using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Unit Economics Ecom + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/vip-program/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/vip-program/SKILL.md new file mode 100644 index 0000000..acf97c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/vip-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a vip program with structured process, quality checks, and system integration +--- + +# Vip Program + +## Purpose + +Design and document a comprehensive vip program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vip program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vip program +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vip program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Vip Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/wholesale-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/wholesale-strategy/SKILL.md new file mode 100644 index 0000000..724cb3a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/wholesale-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a wholesale strategy with structured process, quality checks, and system integration +--- + +# Wholesale Strategy + +## Purpose + +Design and document a comprehensive wholesale strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wholesale strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wholesale strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wholesale strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Wholesale Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/ecommerce/woocommerce-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/ecommerce/woocommerce-setup/SKILL.md new file mode 100644 index 0000000..1667e6b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/ecommerce/woocommerce-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a woocommerce setup with structured process, quality checks, and system integration +--- + +# Woocommerce Setup + +## Purpose + +Design and document a comprehensive woocommerce setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: E-commerce + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing woocommerce setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Conversion Rate Optimization (CRO), RFM Segmentation, Customer Lifetime Value Model + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the woocommerce setup +- Identify gaps, opportunities, and risks +- Define success metrics: Conversion Rate (benchmark: 2-4%), Average Order Value, Cart Abandonment Rate (benchmark: 70%), Customer Acquisition Cost +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the woocommerce setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Optimize for mobile first (60%+ of traffic) + +## Output Format + +```markdown +# Woocommerce Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Conversion Rate Optimization (CRO) +- RFM Segmentation +- Customer Lifetime Value Model +- Merchandising Calendar +- Inventory Planning (ABC Analysis) + +## Key Metrics +- Conversion Rate (benchmark: 2-4%) +- Average Order Value +- Cart Abandonment Rate (benchmark: 70%) +- Customer Acquisition Cost +- Customer Lifetime Value +- Return Rate +- Inventory Turnover + +## Best Practices +- Optimize for mobile first (60%+ of traffic) +- Reduce checkout steps (3 max) +- Show social proof near buy buttons +- Free shipping threshold above AOV +- Abandoned cart emails within 1 hour + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/assessment-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/assessment-design/SKILL.md new file mode 100644 index 0000000..04866f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/assessment-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a assessment design with structured process, quality checks, and system integration +--- + +# Assessment Design + +## Purpose + +Analyze and produce a comprehensive assessment design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing assessment design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the assessment design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the assessment design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Assessment Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/badge-system/SKILL.md b/clowdex-download/.claude/.claude/skills/education/badge-system/SKILL.md new file mode 100644 index 0000000..f41e417 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/badge-system/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a badge system with structured process, quality checks, and system integration +--- + +# Badge System + +## Purpose + +Design and document a comprehensive badge system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing badge system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the badge system +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the badge system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Badge System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/case-study-teaching/SKILL.md b/clowdex-download/.claude/.claude/skills/education/case-study-teaching/SKILL.md new file mode 100644 index 0000000..c3fc3fd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/case-study-teaching/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a case study teaching with structured process, quality checks, and system integration +--- + +# Case Study Teaching + +## Purpose + +Create a comprehensive case study teaching that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing case study teaching documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the case study teaching +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the case study teaching using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Case Study Teaching + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/certification-program-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/certification-program-design/SKILL.md new file mode 100644 index 0000000..88a660d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/certification-program-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a certification program design with structured process, quality checks, and system integration +--- + +# Certification Program Design + +## Purpose + +Create a comprehensive certification program design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing certification program design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the certification program design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the certification program design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Certification Program Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/coaching-program/SKILL.md b/clowdex-download/.claude/.claude/skills/education/coaching-program/SKILL.md new file mode 100644 index 0000000..7cd4b56 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/coaching-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a coaching program with structured process, quality checks, and system integration +--- + +# Coaching Program + +## Purpose + +Design and document a comprehensive coaching program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing coaching program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the coaching program +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the coaching program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Coaching Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/cohort-based-course/SKILL.md b/clowdex-download/.claude/.claude/skills/education/cohort-based-course/SKILL.md new file mode 100644 index 0000000..8296710 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/cohort-based-course/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cohort based course with structured process, quality checks, and system integration +--- + +# Cohort Based Course + +## Purpose + +Create a comprehensive cohort based course that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cohort based course documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cohort based course +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cohort based course using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Cohort Based Course + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/competency-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/education/competency-framework/SKILL.md new file mode 100644 index 0000000..1cbec1d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/competency-framework/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a competency framework with structured process, quality checks, and system integration +--- + +# Competency Framework + +## Purpose + +Design and document a comprehensive competency framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competency framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competency framework +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competency framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Competency Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/compliance-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/compliance-training/SKILL.md new file mode 100644 index 0000000..f541fd1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/compliance-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a compliance training with structured process, quality checks, and system integration +--- + +# Compliance Training + +## Purpose + +Create a comprehensive compliance training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Compliance Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/content-accessibility/SKILL.md b/clowdex-download/.claude/.claude/skills/education/content-accessibility/SKILL.md new file mode 100644 index 0000000..aded31f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/content-accessibility/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content accessibility with structured process, quality checks, and system integration +--- + +# Content Accessibility + +## Purpose + +Create a comprehensive content accessibility that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content accessibility documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content accessibility +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content accessibility using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Content Accessibility + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/corporate-training-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/education/corporate-training-plan/SKILL.md new file mode 100644 index 0000000..70c62e7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/corporate-training-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a corporate training plan with structured process, quality checks, and system integration +--- + +# Corporate Training Plan + +## Purpose + +Design and document a comprehensive corporate training plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate training plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate training plan +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate training plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Corporate Training Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/course-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/education/course-evaluation/SKILL.md new file mode 100644 index 0000000..7d4c24d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/course-evaluation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a course evaluation with structured process, quality checks, and system integration +--- + +# Course Evaluation + +## Purpose + +Analyze and produce a comprehensive course evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing course evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the course evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the course evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Course Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/course-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/education/course-marketing-plan/SKILL.md new file mode 100644 index 0000000..3a25678 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/course-marketing-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a course marketing plan with structured process, quality checks, and system integration +--- + +# Course Marketing Plan + +## Purpose + +Design and document a comprehensive course marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing course marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the course marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the course marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Course Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/course-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/education/course-outline/SKILL.md new file mode 100644 index 0000000..55eb386 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/course-outline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a course outline with structured process, quality checks, and system integration +--- + +# Course Outline + +## Purpose + +Create a comprehensive course outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing course outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the course outline +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the course outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Course Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/credentialing-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/education/credentialing-framework/SKILL.md new file mode 100644 index 0000000..769f8f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/credentialing-framework/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a credentialing framework with structured process, quality checks, and system integration +--- + +# Credentialing Framework + +## Purpose + +Design and document a comprehensive credentialing framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing credentialing framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the credentialing framework +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the credentialing framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Credentialing Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/curriculum-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/curriculum-design/SKILL.md new file mode 100644 index 0000000..094b40b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/curriculum-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a curriculum design with structured process, quality checks, and system integration +--- + +# Curriculum Design + +## Purpose + +Create a comprehensive curriculum design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing curriculum design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the curriculum design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the curriculum design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Curriculum Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/customer-service-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/customer-service-training/SKILL.md new file mode 100644 index 0000000..fb09080 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/customer-service-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer service training with structured process, quality checks, and system integration +--- + +# Customer Service Training + +## Purpose + +Create a comprehensive customer service training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer service training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer service training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer service training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Customer Service Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/educational-content-review/SKILL.md b/clowdex-download/.claude/.claude/skills/education/educational-content-review/SKILL.md new file mode 100644 index 0000000..aca5301 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/educational-content-review/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a educational content review with structured process, quality checks, and system integration +--- + +# Educational Content Review + +## Purpose + +Analyze and produce a comprehensive educational content review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing educational content review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the educational content review +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the educational content review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Educational Content Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/exam-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/education/exam-prep/SKILL.md new file mode 100644 index 0000000..047522f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/exam-prep/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a exam prep with structured process, quality checks, and system integration +--- + +# Exam Prep + +## Purpose + +Create a comprehensive exam prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing exam prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the exam prep +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the exam prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Exam Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/leadership-development/SKILL.md b/clowdex-download/.claude/.claude/skills/education/leadership-development/SKILL.md new file mode 100644 index 0000000..b9f2336 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/leadership-development/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a leadership development with structured process, quality checks, and system integration +--- + +# Leadership Development + +## Purpose + +Create a comprehensive leadership development that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing leadership development documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the leadership development +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the leadership development using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Leadership Development + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/learning-analytics/SKILL.md b/clowdex-download/.claude/.claude/skills/education/learning-analytics/SKILL.md new file mode 100644 index 0000000..393dfda --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/learning-analytics/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a learning analytics with structured process, quality checks, and system integration +--- + +# Learning Analytics + +## Purpose + +Create a comprehensive learning analytics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing learning analytics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the learning analytics +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the learning analytics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Learning Analytics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/learning-objectives/SKILL.md b/clowdex-download/.claude/.claude/skills/education/learning-objectives/SKILL.md new file mode 100644 index 0000000..aa3989a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/learning-objectives/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a learning objectives with structured process, quality checks, and system integration +--- + +# Learning Objectives + +## Purpose + +Create a comprehensive learning objectives that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing learning objectives documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the learning objectives +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the learning objectives using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Learning Objectives + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/learning-path/SKILL.md b/clowdex-download/.claude/.claude/skills/education/learning-path/SKILL.md new file mode 100644 index 0000000..985b46e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/learning-path/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a learning path with structured process, quality checks, and system integration +--- + +# Learning Path + +## Purpose + +Create a comprehensive learning path that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing learning path documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the learning path +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the learning path using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Learning Path + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/lesson-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/education/lesson-plan/SKILL.md new file mode 100644 index 0000000..e21125b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/lesson-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a lesson plan with structured process, quality checks, and system integration +--- + +# Lesson Plan + +## Purpose + +Design and document a comprehensive lesson plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lesson plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lesson plan +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lesson plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Lesson Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/live-session-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/education/live-session-plan/SKILL.md new file mode 100644 index 0000000..9870d34 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/live-session-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a live session plan with structured process, quality checks, and system integration +--- + +# Live Session Plan + +## Purpose + +Design and document a comprehensive live session plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing live session plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the live session plan +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the live session plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Live Session Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/lms-content-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/education/lms-content-plan/SKILL.md new file mode 100644 index 0000000..c3f29cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/lms-content-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a lms content plan with structured process, quality checks, and system integration +--- + +# Lms Content Plan + +## Purpose + +Design and document a comprehensive lms content plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lms content plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lms content plan +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lms content plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Lms Content Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/management-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/management-training/SKILL.md new file mode 100644 index 0000000..de4ba28 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/management-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a management training with structured process, quality checks, and system integration +--- + +# Management Training + +## Purpose + +Create a comprehensive management training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing management training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the management training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the management training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Management Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/mentorship-program/SKILL.md b/clowdex-download/.claude/.claude/skills/education/mentorship-program/SKILL.md new file mode 100644 index 0000000..af26cfb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/mentorship-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a mentorship program with structured process, quality checks, and system integration +--- + +# Mentorship Program + +## Purpose + +Design and document a comprehensive mentorship program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mentorship program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mentorship program +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mentorship program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Mentorship Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/microlearning-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/microlearning-design/SKILL.md new file mode 100644 index 0000000..556ff2c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/microlearning-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a microlearning design with structured process, quality checks, and system integration +--- + +# Microlearning Design + +## Purpose + +Create a comprehensive microlearning design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing microlearning design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the microlearning design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the microlearning design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Microlearning Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/module-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/module-design/SKILL.md new file mode 100644 index 0000000..2b0a0bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/module-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a module design with structured process, quality checks, and system integration +--- + +# Module Design + +## Purpose + +Create a comprehensive module design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing module design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the module design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the module design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Module Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/office-hours-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/education/office-hours-structure/SKILL.md new file mode 100644 index 0000000..3ba3e1f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/office-hours-structure/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a office hours structure with structured process, quality checks, and system integration +--- + +# Office Hours Structure + +## Purpose + +Create a comprehensive office hours structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing office hours structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the office hours structure +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the office hours structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Office Hours Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/onboarding-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/onboarding-training/SKILL.md new file mode 100644 index 0000000..b652f6c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/onboarding-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a onboarding training with structured process, quality checks, and system integration +--- + +# Onboarding Training + +## Purpose + +Create a comprehensive onboarding training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Onboarding Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/online-course-launch/SKILL.md b/clowdex-download/.claude/.claude/skills/education/online-course-launch/SKILL.md new file mode 100644 index 0000000..8e2c996 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/online-course-launch/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a online course launch with structured process, quality checks, and system integration +--- + +# Online Course Launch + +## Purpose + +Create a comprehensive online course launch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing online course launch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the online course launch +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the online course launch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Online Course Launch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/peer-learning-program/SKILL.md b/clowdex-download/.claude/.claude/skills/education/peer-learning-program/SKILL.md new file mode 100644 index 0000000..69cf671 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/peer-learning-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a peer learning program with structured process, quality checks, and system integration +--- + +# Peer Learning Program + +## Purpose + +Design and document a comprehensive peer learning program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing peer learning program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the peer learning program +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the peer learning program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Peer Learning Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/quiz-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/education/quiz-generator/SKILL.md new file mode 100644 index 0000000..da860fb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/quiz-generator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a quiz generator with structured process, quality checks, and system integration +--- + +# Quiz Generator + +## Purpose + +Create a comprehensive quiz generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quiz generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quiz generator +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quiz generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Quiz Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/role-play-scenario-edu/SKILL.md b/clowdex-download/.claude/.claude/skills/education/role-play-scenario-edu/SKILL.md new file mode 100644 index 0000000..1f76ac0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/role-play-scenario-edu/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a role play scenario edu with structured process, quality checks, and system integration +--- + +# Role Play Scenario Edu + +## Purpose + +Create a comprehensive role play scenario edu that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing role play scenario edu documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the role play scenario edu +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the role play scenario edu using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Role Play Scenario Edu + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/rubric-creator/SKILL.md b/clowdex-download/.claude/.claude/skills/education/rubric-creator/SKILL.md new file mode 100644 index 0000000..d4142c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/rubric-creator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a rubric creator with structured process, quality checks, and system integration +--- + +# Rubric Creator + +## Purpose + +Create a comprehensive rubric creator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rubric creator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rubric creator +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rubric creator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Rubric Creator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/sales-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/sales-training/SKILL.md new file mode 100644 index 0000000..374ba7a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/sales-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a sales training with structured process, quality checks, and system integration +--- + +# Sales Training + +## Purpose + +Create a comprehensive sales training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Sales Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/scorm-module-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/education/scorm-module-spec/SKILL.md new file mode 100644 index 0000000..a119075 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/scorm-module-spec/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a scorm module spec with structured process, quality checks, and system integration +--- + +# Scorm Module Spec + +## Purpose + +Create a comprehensive scorm module spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scorm module spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scorm module spec +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scorm module spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Scorm Module Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/simulation-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/simulation-design/SKILL.md new file mode 100644 index 0000000..d69a70b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/simulation-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a simulation design with structured process, quality checks, and system integration +--- + +# Simulation Design + +## Purpose + +Create a comprehensive simulation design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing simulation design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the simulation design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the simulation design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Simulation Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/skills-gap-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/education/skills-gap-analysis/SKILL.md new file mode 100644 index 0000000..0e6a25e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/skills-gap-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a skills gap analysis with structured process, quality checks, and system integration +--- + +# Skills Gap Analysis + +## Purpose + +Analyze and produce a comprehensive skills gap analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing skills gap analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the skills gap analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the skills gap analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Skills Gap Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/soft-skills-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/soft-skills-training/SKILL.md new file mode 100644 index 0000000..542c812 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/soft-skills-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a soft skills training with structured process, quality checks, and system integration +--- + +# Soft Skills Training + +## Purpose + +Create a comprehensive soft skills training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing soft skills training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the soft skills training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the soft skills training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Soft Skills Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/student-feedback-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/education/student-feedback-survey/SKILL.md new file mode 100644 index 0000000..927e2aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/student-feedback-survey/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a student feedback survey with structured process, quality checks, and system integration +--- + +# Student Feedback Survey + +## Purpose + +Create a comprehensive student feedback survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing student feedback survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the student feedback survey +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the student feedback survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Student Feedback Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/student-onboarding/SKILL.md b/clowdex-download/.claude/.claude/skills/education/student-onboarding/SKILL.md new file mode 100644 index 0000000..6d370c7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/student-onboarding/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a student onboarding with structured process, quality checks, and system integration +--- + +# Student Onboarding + +## Purpose + +Create a comprehensive student onboarding that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing student onboarding documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the student onboarding +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the student onboarding using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Student Onboarding + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/study-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/education/study-guide/SKILL.md new file mode 100644 index 0000000..48fe438 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/study-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a study guide with structured process, quality checks, and system integration +--- + +# Study Guide + +## Purpose + +Design and document a comprehensive study guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing study guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the study guide +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the study guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Study Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/technical-training/SKILL.md b/clowdex-download/.claude/.claude/skills/education/technical-training/SKILL.md new file mode 100644 index 0000000..5139ce6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/technical-training/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a technical training with structured process, quality checks, and system integration +--- + +# Technical Training + +## Purpose + +Create a comprehensive technical training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technical training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technical training +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technical training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Technical Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/training-needs-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/education/training-needs-assessment/SKILL.md new file mode 100644 index 0000000..d1b8109 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/training-needs-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a training needs assessment with structured process, quality checks, and system integration +--- + +# Training Needs Assessment + +## Purpose + +Analyze and produce a comprehensive training needs assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing training needs assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the training needs assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the training needs assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Training Needs Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/tutoring-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/education/tutoring-guide/SKILL.md new file mode 100644 index 0000000..52567f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/tutoring-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a tutoring guide with structured process, quality checks, and system integration +--- + +# Tutoring Guide + +## Purpose + +Design and document a comprehensive tutoring guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tutoring guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tutoring guide +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tutoring guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Tutoring Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/universal-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/universal-design/SKILL.md new file mode 100644 index 0000000..5db7df0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/universal-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a universal design with structured process, quality checks, and system integration +--- + +# Universal Design + +## Purpose + +Create a comprehensive universal design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing universal design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the universal design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the universal design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Universal Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/workshop-design/SKILL.md b/clowdex-download/.claude/.claude/skills/education/workshop-design/SKILL.md new file mode 100644 index 0000000..99ff3b1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/workshop-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a workshop design with structured process, quality checks, and system integration +--- + +# Workshop Design + +## Purpose + +Create a comprehensive workshop design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workshop design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workshop design +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workshop design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Workshop Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/workshop-facilitator-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/education/workshop-facilitator-guide/SKILL.md new file mode 100644 index 0000000..016a5a0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/workshop-facilitator-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a workshop facilitator guide with structured process, quality checks, and system integration +--- + +# Workshop Facilitator Guide + +## Purpose + +Design and document a comprehensive workshop facilitator guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workshop facilitator guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workshop facilitator guide +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workshop facilitator guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Workshop Facilitator Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/education/workshop-materials/SKILL.md b/clowdex-download/.claude/.claude/skills/education/workshop-materials/SKILL.md new file mode 100644 index 0000000..68a1ce6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/education/workshop-materials/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a workshop materials with structured process, quality checks, and system integration +--- + +# Workshop Materials + +## Purpose + +Create a comprehensive workshop materials that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Education & Training + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workshop materials documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Bloom's Taxonomy, ADDIE (Analyze, Design, Develop, Implement, Evaluate), Kirkpatrick Four Levels + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workshop materials +- Identify gaps, opportunities, and risks +- Define success metrics: Completion Rate, Assessment Scores, Knowledge Retention, Learner Satisfaction +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workshop materials using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Start with learning objectives (what will they DO) + +## Output Format + +```markdown +# Workshop Materials + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Bloom's Taxonomy +- ADDIE (Analyze, Design, Develop, Implement, Evaluate) +- Kirkpatrick Four Levels +- Backwards Design +- Universal Design for Learning +- Spaced Repetition + +## Key Metrics +- Completion Rate +- Assessment Scores +- Knowledge Retention +- Learner Satisfaction +- Time to Competency +- Application Rate (on-the-job) + +## Best Practices +- Start with learning objectives (what will they DO) +- Chunk content into 5-7 minute segments +- Mix modalities (read, watch, do, discuss) +- Assessment aligned to objectives +- Follow up at 30, 60, 90 days for retention + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/announcement-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/announcement-email/SKILL.md new file mode 100644 index 0000000..c32e46d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/announcement-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a announcement email with structured process, quality checks, and system integration +--- + +# Announcement Email + +## Purpose + +Create a comprehensive announcement email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing announcement email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the announcement email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the announcement email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Announcement Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/browse-abandonment-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/browse-abandonment-sequence/SKILL.md new file mode 100644 index 0000000..4f58842 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/browse-abandonment-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a browse abandonment sequence with structured process, quality checks, and system integration +--- + +# Browse Abandonment Sequence + +## Purpose + +Create a comprehensive browse abandonment sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing browse abandonment sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the browse abandonment sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the browse abandonment sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Browse Abandonment Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/can-spam-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/email/can-spam-checklist/SKILL.md new file mode 100644 index 0000000..0b4574a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/can-spam-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a can spam checklist with structured process, quality checks, and system integration +--- + +# Can Spam Checklist + +## Purpose + +Analyze and produce a comprehensive can spam checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing can spam checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the can spam checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the can spam checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Can Spam Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/cart-abandonment-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/cart-abandonment-sequence/SKILL.md new file mode 100644 index 0000000..d151d64 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/cart-abandonment-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cart abandonment sequence with structured process, quality checks, and system integration +--- + +# Cart Abandonment Sequence + +## Purpose + +Create a comprehensive cart abandonment sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cart abandonment sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cart abandonment sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cart abandonment sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Cart Abandonment Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/cold-outreach-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/cold-outreach-email/SKILL.md new file mode 100644 index 0000000..6ba8e66 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/cold-outreach-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cold outreach email with structured process, quality checks, and system integration +--- + +# Cold Outreach Email + +## Purpose + +Create a comprehensive cold outreach email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cold outreach email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cold outreach email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cold outreach email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Cold Outreach Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/confirmation-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/confirmation-email/SKILL.md new file mode 100644 index 0000000..7fb7601 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/confirmation-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a confirmation email with structured process, quality checks, and system integration +--- + +# Confirmation Email + +## Purpose + +Create a comprehensive confirmation email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing confirmation email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the confirmation email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the confirmation email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Confirmation Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/deliverability-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/email/deliverability-audit/SKILL.md new file mode 100644 index 0000000..8741f9b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/deliverability-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a deliverability audit with structured process, quality checks, and system integration +--- + +# Deliverability Audit + +## Purpose + +Analyze and produce a comprehensive deliverability audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deliverability audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deliverability audit +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deliverability audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Deliverability Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/domain-reputation-fix/SKILL.md b/clowdex-download/.claude/.claude/skills/email/domain-reputation-fix/SKILL.md new file mode 100644 index 0000000..685a8a3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/domain-reputation-fix/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a domain reputation fix with structured process, quality checks, and system integration +--- + +# Domain Reputation Fix + +## Purpose + +Create a comprehensive domain reputation fix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing domain reputation fix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the domain reputation fix +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the domain reputation fix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Domain Reputation Fix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-ab-test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-ab-test-plan/SKILL.md new file mode 100644 index 0000000..991884f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-ab-test-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a email ab test plan with structured process, quality checks, and system integration +--- + +# Email Ab Test Plan + +## Purpose + +Design and document a comprehensive email ab test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email ab test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email ab test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email ab test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Ab Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-analytics-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-analytics-dashboard/SKILL.md new file mode 100644 index 0000000..353252e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-analytics-dashboard/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a email analytics dashboard with structured process, quality checks, and system integration +--- + +# Email Analytics Dashboard + +## Purpose + +Analyze and produce a comprehensive email analytics dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email analytics dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email analytics dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email analytics dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Analytics Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-automation-workflow/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-automation-workflow/SKILL.md new file mode 100644 index 0000000..2c7ce72 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-automation-workflow/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a email automation workflow with structured process, quality checks, and system integration +--- + +# Email Automation Workflow + +## Purpose + +Design and document a comprehensive email automation workflow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email automation workflow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email automation workflow +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email automation workflow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Automation Workflow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-benchmark-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-benchmark-analysis/SKILL.md new file mode 100644 index 0000000..43565bd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-benchmark-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a email benchmark analysis with structured process, quality checks, and system integration +--- + +# Email Benchmark Analysis + +## Purpose + +Analyze and produce a comprehensive email benchmark analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email benchmark analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email benchmark analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email benchmark analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Benchmark Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-compliance-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-compliance-audit/SKILL.md new file mode 100644 index 0000000..b3acb7c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-compliance-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a email compliance audit with structured process, quality checks, and system integration +--- + +# Email Compliance Audit + +## Purpose + +Analyze and produce a comprehensive email compliance audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email compliance audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email compliance audit +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email compliance audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Compliance Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-optimization-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-optimization-audit/SKILL.md new file mode 100644 index 0000000..66558fa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-optimization-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a email optimization audit with structured process, quality checks, and system integration +--- + +# Email Optimization Audit + +## Purpose + +Analyze and produce a comprehensive email optimization audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email optimization audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email optimization audit +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email optimization audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Optimization Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-reporting-template/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-reporting-template/SKILL.md new file mode 100644 index 0000000..5235821 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-reporting-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a email reporting template with structured process, quality checks, and system integration +--- + +# Email Reporting Template + +## Purpose + +Analyze and produce a comprehensive email reporting template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email reporting template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email reporting template +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email reporting template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Reporting Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-segmentation-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-segmentation-strategy/SKILL.md new file mode 100644 index 0000000..3cf6e67 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-segmentation-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a email segmentation strategy with structured process, quality checks, and system integration +--- + +# Email Segmentation Strategy + +## Purpose + +Design and document a comprehensive email segmentation strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email segmentation strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email segmentation strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email segmentation strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Segmentation Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-subject-line-testing/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-subject-line-testing/SKILL.md new file mode 100644 index 0000000..f95e9b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-subject-line-testing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a email subject line testing with structured process, quality checks, and system integration +--- + +# Email Subject Line Testing + +## Purpose + +Create a comprehensive email subject line testing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email subject line testing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email subject line testing +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email subject line testing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Subject Line Testing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/email-template-design-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/email/email-template-design-brief/SKILL.md new file mode 100644 index 0000000..e2c4271 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/email-template-design-brief/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a email template design brief with structured process, quality checks, and system integration +--- + +# Email Template Design Brief + +## Purpose + +Create a comprehensive email template design brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email template design brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email template design brief +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email template design brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Email Template Design Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/event-invitation-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/event-invitation-email/SKILL.md new file mode 100644 index 0000000..1e63379 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/event-invitation-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a event invitation email with structured process, quality checks, and system integration +--- + +# Event Invitation Email + +## Purpose + +Create a comprehensive event invitation email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event invitation email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event invitation email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event invitation email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Event Invitation Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/feature-launch-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/feature-launch-email/SKILL.md new file mode 100644 index 0000000..6bad1e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/feature-launch-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a feature launch email with structured process, quality checks, and system integration +--- + +# Feature Launch Email + +## Purpose + +Create a comprehensive feature launch email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature launch email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature launch email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature launch email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Feature Launch Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/flash-sale-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/flash-sale-email/SKILL.md new file mode 100644 index 0000000..21e9cc4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/flash-sale-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a flash sale email with structured process, quality checks, and system integration +--- + +# Flash Sale Email + +## Purpose + +Create a comprehensive flash sale email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing flash sale email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the flash sale email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the flash sale email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Flash Sale Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/gdpr-email-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/email/gdpr-email-checklist/SKILL.md new file mode 100644 index 0000000..0e17d0a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/gdpr-email-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a gdpr email checklist with structured process, quality checks, and system integration +--- + +# Gdpr Email Checklist + +## Purpose + +Analyze and produce a comprehensive gdpr email checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gdpr email checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gdpr email checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gdpr email checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Gdpr Email Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/html-email-spec/SKILL.md b/clowdex-download/.claude/.claude/skills/email/html-email-spec/SKILL.md new file mode 100644 index 0000000..1cb8ead --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/html-email-spec/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a html email spec with structured process, quality checks, and system integration +--- + +# Html Email Spec + +## Purpose + +Create a comprehensive html email spec that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing html email spec documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the html email spec +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the html email spec using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Html Email Spec + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/launch-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/launch-sequence/SKILL.md new file mode 100644 index 0000000..52fb033 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/launch-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a launch sequence with structured process, quality checks, and system integration +--- + +# Launch Sequence + +## Purpose + +Create a comprehensive launch sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing launch sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the launch sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the launch sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Launch Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/lifecycle-email-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/email/lifecycle-email-strategy/SKILL.md new file mode 100644 index 0000000..171783d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/lifecycle-email-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a lifecycle email strategy with structured process, quality checks, and system integration +--- + +# Lifecycle Email Strategy + +## Purpose + +Design and document a comprehensive lifecycle email strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lifecycle email strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lifecycle email strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lifecycle email strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Lifecycle Email Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/list-cleaning-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/email/list-cleaning-plan/SKILL.md new file mode 100644 index 0000000..d3fea4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/list-cleaning-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a list cleaning plan with structured process, quality checks, and system integration +--- + +# List Cleaning Plan + +## Purpose + +Design and document a comprehensive list cleaning plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing list cleaning plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the list cleaning plan +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the list cleaning plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# List Cleaning Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/newsletter-editorial-calendar/SKILL.md b/clowdex-download/.claude/.claude/skills/email/newsletter-editorial-calendar/SKILL.md new file mode 100644 index 0000000..f951648 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/newsletter-editorial-calendar/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a newsletter editorial calendar with structured process, quality checks, and system integration +--- + +# Newsletter Editorial Calendar + +## Purpose + +Design and document a comprehensive newsletter editorial calendar that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter editorial calendar documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter editorial calendar +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter editorial calendar using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Newsletter Editorial Calendar + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/newsletter-growth-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/email/newsletter-growth-strategy/SKILL.md new file mode 100644 index 0000000..88e1e09 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/newsletter-growth-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a newsletter growth strategy with structured process, quality checks, and system integration +--- + +# Newsletter Growth Strategy + +## Purpose + +Design and document a comprehensive newsletter growth strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter growth strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter growth strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter growth strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Newsletter Growth Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/newsletter-template/SKILL.md b/clowdex-download/.claude/.claude/skills/email/newsletter-template/SKILL.md new file mode 100644 index 0000000..37fb868 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/newsletter-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a newsletter template with structured process, quality checks, and system integration +--- + +# Newsletter Template + +## Purpose + +Create a comprehensive newsletter template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter template +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Newsletter Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/nurture-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/nurture-sequence/SKILL.md new file mode 100644 index 0000000..4990bdf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/nurture-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a nurture sequence with structured process, quality checks, and system integration +--- + +# Nurture Sequence + +## Purpose + +Create a comprehensive nurture sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nurture sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nurture sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nurture sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Nurture Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/onboarding-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/onboarding-sequence/SKILL.md new file mode 100644 index 0000000..ad77add --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/onboarding-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a onboarding sequence with structured process, quality checks, and system integration +--- + +# Onboarding Sequence + +## Purpose + +Create a comprehensive onboarding sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Onboarding Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/partnership-outreach-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/partnership-outreach-email/SKILL.md new file mode 100644 index 0000000..ea8dc9b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/partnership-outreach-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a partnership outreach email with structured process, quality checks, and system integration +--- + +# Partnership Outreach Email + +## Purpose + +Create a comprehensive partnership outreach email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing partnership outreach email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the partnership outreach email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the partnership outreach email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Partnership Outreach Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/password-reset-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/password-reset-email/SKILL.md new file mode 100644 index 0000000..17635e2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/password-reset-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a password reset email with structured process, quality checks, and system integration +--- + +# Password Reset Email + +## Purpose + +Create a comprehensive password reset email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing password reset email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the password reset email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the password reset email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Password Reset Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/plain-text-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/plain-text-email/SKILL.md new file mode 100644 index 0000000..e4212df --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/plain-text-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a plain text email with structured process, quality checks, and system integration +--- + +# Plain Text Email + +## Purpose + +Create a comprehensive plain text email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing plain text email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the plain text email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the plain text email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Plain Text Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/post-event-follow-up/SKILL.md b/clowdex-download/.claude/.claude/skills/email/post-event-follow-up/SKILL.md new file mode 100644 index 0000000..7c50746 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/post-event-follow-up/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a post event follow up with structured process, quality checks, and system integration +--- + +# Post Event Follow Up + +## Purpose + +Create a comprehensive post event follow up that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing post event follow up documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the post event follow up +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the post event follow up using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Post Event Follow Up + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/post-purchase-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/post-purchase-sequence/SKILL.md new file mode 100644 index 0000000..916ef9b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/post-purchase-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a post purchase sequence with structured process, quality checks, and system integration +--- + +# Post Purchase Sequence + +## Purpose + +Create a comprehensive post purchase sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing post purchase sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the post purchase sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the post purchase sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Post Purchase Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/pr-outreach-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/pr-outreach-email/SKILL.md new file mode 100644 index 0000000..49bd436 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/pr-outreach-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a pr outreach email with structured process, quality checks, and system integration +--- + +# Pr Outreach Email + +## Purpose + +Create a comprehensive pr outreach email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pr outreach email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pr outreach email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pr outreach email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Pr Outreach Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/product-update-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/product-update-email/SKILL.md new file mode 100644 index 0000000..a0e15a7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/product-update-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a product update email with structured process, quality checks, and system integration +--- + +# Product Update Email + +## Purpose + +Create a comprehensive product update email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product update email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product update email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product update email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Product Update Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/promotional-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/promotional-email/SKILL.md new file mode 100644 index 0000000..6991e01 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/promotional-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a promotional email with structured process, quality checks, and system integration +--- + +# Promotional Email + +## Purpose + +Create a comprehensive promotional email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing promotional email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the promotional email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the promotional email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Promotional Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/re-engagement-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/re-engagement-sequence/SKILL.md new file mode 100644 index 0000000..2f9e9f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/re-engagement-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a re engagement sequence with structured process, quality checks, and system integration +--- + +# Re Engagement Sequence + +## Purpose + +Create a comprehensive re engagement sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing re engagement sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the re engagement sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the re engagement sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Re Engagement Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/referral-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/referral-sequence/SKILL.md new file mode 100644 index 0000000..f8a2249 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/referral-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a referral sequence with structured process, quality checks, and system integration +--- + +# Referral Sequence + +## Purpose + +Create a comprehensive referral sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Referral Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/review-request-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/review-request-sequence/SKILL.md new file mode 100644 index 0000000..2def64c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/review-request-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a review request sequence with structured process, quality checks, and system integration +--- + +# Review Request Sequence + +## Purpose + +Analyze and produce a comprehensive review request sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review request sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review request sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review request sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Review Request Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/seasonal-email/SKILL.md b/clowdex-download/.claude/.claude/skills/email/seasonal-email/SKILL.md new file mode 100644 index 0000000..9f336e9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/seasonal-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a seasonal email with structured process, quality checks, and system integration +--- + +# Seasonal Email + +## Purpose + +Create a comprehensive seasonal email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seasonal email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seasonal email +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seasonal email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Seasonal Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/subscriber-scoring/SKILL.md b/clowdex-download/.claude/.claude/skills/email/subscriber-scoring/SKILL.md new file mode 100644 index 0000000..dfd6177 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/subscriber-scoring/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a subscriber scoring with structured process, quality checks, and system integration +--- + +# Subscriber Scoring + +## Purpose + +Analyze and produce a comprehensive subscriber scoring that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subscriber scoring documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subscriber scoring +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subscriber scoring using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Subscriber Scoring + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/sunset-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/sunset-sequence/SKILL.md new file mode 100644 index 0000000..79155e7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/sunset-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a sunset sequence with structured process, quality checks, and system integration +--- + +# Sunset Sequence + +## Purpose + +Create a comprehensive sunset sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sunset sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sunset sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sunset sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Sunset Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/transactional-email-copy/SKILL.md b/clowdex-download/.claude/.claude/skills/email/transactional-email-copy/SKILL.md new file mode 100644 index 0000000..6c9ffb5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/transactional-email-copy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a transactional email copy with structured process, quality checks, and system integration +--- + +# Transactional Email Copy + +## Purpose + +Create a comprehensive transactional email copy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing transactional email copy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the transactional email copy +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the transactional email copy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Transactional Email Copy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/trigger-email-map/SKILL.md b/clowdex-download/.claude/.claude/skills/email/trigger-email-map/SKILL.md new file mode 100644 index 0000000..5334e1f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/trigger-email-map/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a trigger email map with structured process, quality checks, and system integration +--- + +# Trigger Email Map + +## Purpose + +Create a comprehensive trigger email map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trigger email map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trigger email map +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trigger email map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Trigger Email Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/warm-up-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/email/warm-up-plan/SKILL.md new file mode 100644 index 0000000..15ad288 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/warm-up-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a warm up plan with structured process, quality checks, and system integration +--- + +# Warm Up Plan + +## Purpose + +Design and document a comprehensive warm up plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing warm up plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the warm up plan +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the warm up plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Warm Up Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/webinar-reminder-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/webinar-reminder-sequence/SKILL.md new file mode 100644 index 0000000..a7fe2c5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/webinar-reminder-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a webinar reminder sequence with structured process, quality checks, and system integration +--- + +# Webinar Reminder Sequence + +## Purpose + +Create a comprehensive webinar reminder sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing webinar reminder sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the webinar reminder sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the webinar reminder sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Webinar Reminder Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/welcome-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/welcome-sequence/SKILL.md new file mode 100644 index 0000000..7f54f76 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/welcome-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a welcome sequence with structured process, quality checks, and system integration +--- + +# Welcome Sequence + +## Purpose + +Create a comprehensive welcome sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing welcome sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the welcome sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the welcome sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Welcome Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/email/win-back-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/email/win-back-sequence/SKILL.md new file mode 100644 index 0000000..af9bf88 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/email/win-back-sequence/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a win back sequence with structured process, quality checks, and system integration +--- + +# Win Back Sequence + +## Purpose + +Create a comprehensive win back sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Email Marketing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing win back sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Welcome → Nurture → Convert → Retain lifecycle, Segmentation Ladder, RFM (Recency, Frequency, Monetary) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the win back sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Open Rate (benchmark: 20-25%), Click Rate (benchmark: 2-5%), Conversion Rate, Unsubscribe Rate (keep under 0.5%) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the win back sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Subject lines under 50 characters + +## Output Format + +```markdown +# Win Back Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Welcome → Nurture → Convert → Retain lifecycle +- Segmentation Ladder +- RFM (Recency, Frequency, Monetary) +- Progressive Profiling +- Behavioral Triggers + +## Key Metrics +- Open Rate (benchmark: 20-25%) +- Click Rate (benchmark: 2-5%) +- Conversion Rate +- Unsubscribe Rate (keep under 0.5%) +- Deliverability Rate (target: 95%+) +- Revenue Per Email + +## Best Practices +- Subject lines under 50 characters +- Preview text is your second headline — never waste it +- One primary CTA per email +- Send time optimization by timezone +- Clean list quarterly (remove 6-month inactive) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/adaptation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/adaptation-plan/SKILL.md new file mode 100644 index 0000000..df3d0f9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/adaptation-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a adaptation plan with structured process, quality checks, and system integration +--- + +# Adaptation Plan + +## Purpose + +Design and document a comprehensive adaptation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing adaptation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the adaptation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the adaptation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Adaptation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/battery-storage-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/battery-storage-analysis/SKILL.md new file mode 100644 index 0000000..344e071 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/battery-storage-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a battery storage analysis with structured process, quality checks, and system integration +--- + +# Battery Storage Analysis + +## Purpose + +Analyze and produce a comprehensive battery storage analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing battery storage analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the battery storage analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the battery storage analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Battery Storage Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/carbon-footprint-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/carbon-footprint-calculator/SKILL.md new file mode 100644 index 0000000..4a0b8e8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/carbon-footprint-calculator/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a carbon footprint calculator with structured process, quality checks, and system integration +--- + +# Carbon Footprint Calculator + +## Purpose + +Create a comprehensive carbon footprint calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing carbon footprint calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the carbon footprint calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the carbon footprint calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Carbon Footprint Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/carbon-offset-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/carbon-offset-strategy/SKILL.md new file mode 100644 index 0000000..dfabab8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/carbon-offset-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a carbon offset strategy with structured process, quality checks, and system integration +--- + +# Carbon Offset Strategy + +## Purpose + +Design and document a comprehensive carbon offset strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing carbon offset strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the carbon offset strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the carbon offset strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Carbon Offset Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/circular-economy-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/circular-economy-assessment/SKILL.md new file mode 100644 index 0000000..68601ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/circular-economy-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a circular economy assessment with structured process, quality checks, and system integration +--- + +# Circular Economy Assessment + +## Purpose + +Analyze and produce a comprehensive circular economy assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing circular economy assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the circular economy assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the circular economy assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Circular Economy Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/climate-risk-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/climate-risk-assessment/SKILL.md new file mode 100644 index 0000000..ee6f96c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/climate-risk-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a climate risk assessment with structured process, quality checks, and system integration +--- + +# Climate Risk Assessment + +## Purpose + +Analyze and produce a comprehensive climate risk assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing climate risk assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the climate risk assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the climate risk assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Climate Risk Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/community-impact/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/community-impact/SKILL.md new file mode 100644 index 0000000..09e5a9c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/community-impact/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a community impact with structured process, quality checks, and system integration +--- + +# Community Impact + +## Purpose + +Create a comprehensive community impact that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing community impact documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the community impact +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the community impact using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Community Impact + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/conservation-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/conservation-strategy/SKILL.md new file mode 100644 index 0000000..1e61261 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/conservation-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a conservation strategy with structured process, quality checks, and system integration +--- + +# Conservation Strategy + +## Purpose + +Design and document a comprehensive conservation strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conservation strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conservation strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conservation strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Conservation Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/energy-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/energy-audit/SKILL.md new file mode 100644 index 0000000..b0c1333 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/energy-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a energy audit with structured process, quality checks, and system integration +--- + +# Energy Audit + +## Purpose + +Analyze and produce a comprehensive energy audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing energy audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the energy audit +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the energy audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Energy Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/energy-management-system/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/energy-management-system/SKILL.md new file mode 100644 index 0000000..9f80109 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/energy-management-system/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a energy management system with structured process, quality checks, and system integration +--- + +# Energy Management System + +## Purpose + +Design and document a comprehensive energy management system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing energy management system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the energy management system +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the energy management system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Energy Management System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/energy-savings-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/energy-savings-plan/SKILL.md new file mode 100644 index 0000000..cd3fec2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/energy-savings-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a energy savings plan with structured process, quality checks, and system integration +--- + +# Energy Savings Plan + +## Purpose + +Design and document a comprehensive energy savings plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing energy savings plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the energy savings plan +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the energy savings plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Energy Savings Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/energy-star-certification/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/energy-star-certification/SKILL.md new file mode 100644 index 0000000..1ed5171 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/energy-star-certification/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a energy star certification with structured process, quality checks, and system integration +--- + +# Energy Star Certification + +## Purpose + +Create a comprehensive energy star certification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing energy star certification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the energy star certification +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the energy star certification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Energy Star Certification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/environmental-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/environmental-compliance/SKILL.md new file mode 100644 index 0000000..58c7a75 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/environmental-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a environmental compliance with structured process, quality checks, and system integration +--- + +# Environmental Compliance + +## Purpose + +Create a comprehensive environmental compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing environmental compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the environmental compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the environmental compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Environmental Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/environmental-impact-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/environmental-impact-assessment/SKILL.md new file mode 100644 index 0000000..cab361c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/environmental-impact-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a environmental impact assessment with structured process, quality checks, and system integration +--- + +# Environmental Impact Assessment + +## Purpose + +Analyze and produce a comprehensive environmental impact assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing environmental impact assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the environmental impact assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the environmental impact assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Environmental Impact Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/esg-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/esg-framework/SKILL.md new file mode 100644 index 0000000..61e2b47 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/esg-framework/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a esg framework with structured process, quality checks, and system integration +--- + +# Esg Framework + +## Purpose + +Design and document a comprehensive esg framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing esg framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the esg framework +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the esg framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Esg Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/ev-fleet-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/ev-fleet-analysis/SKILL.md new file mode 100644 index 0000000..ef9c1cc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/ev-fleet-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a ev fleet analysis with structured process, quality checks, and system integration +--- + +# Ev Fleet Analysis + +## Purpose + +Analyze and produce a comprehensive ev fleet analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ev fleet analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ev fleet analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ev fleet analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Ev Fleet Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/ghg-inventory/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/ghg-inventory/SKILL.md new file mode 100644 index 0000000..4e312cb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/ghg-inventory/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ghg inventory with structured process, quality checks, and system integration +--- + +# Ghg Inventory + +## Purpose + +Create a comprehensive ghg inventory that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ghg inventory documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ghg inventory +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ghg inventory using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Ghg Inventory + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/green-building-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/green-building-checklist/SKILL.md new file mode 100644 index 0000000..99b2e4c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/green-building-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a green building checklist with structured process, quality checks, and system integration +--- + +# Green Building Checklist + +## Purpose + +Analyze and produce a comprehensive green building checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing green building checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the green building checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the green building checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Green Building Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/green-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/green-marketing/SKILL.md new file mode 100644 index 0000000..8226779 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/green-marketing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a green marketing with structured process, quality checks, and system integration +--- + +# Green Marketing + +## Purpose + +Create a comprehensive green marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing green marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the green marketing +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the green marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Green Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/green-vendor-criteria/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/green-vendor-criteria/SKILL.md new file mode 100644 index 0000000..6f82d6d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/green-vendor-criteria/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a green vendor criteria with structured process, quality checks, and system integration +--- + +# Green Vendor Criteria + +## Purpose + +Create a comprehensive green vendor criteria that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing green vendor criteria documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the green vendor criteria +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the green vendor criteria using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Green Vendor Criteria + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/greenwashing-check/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/greenwashing-check/SKILL.md new file mode 100644 index 0000000..34172b1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/greenwashing-check/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a greenwashing check with structured process, quality checks, and system integration +--- + +# Greenwashing Check + +## Purpose + +Analyze and produce a comprehensive greenwashing check that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing greenwashing check documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the greenwashing check +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the greenwashing check using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Greenwashing Check + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/iso-50001-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/iso-50001-prep/SKILL.md new file mode 100644 index 0000000..cf9b49f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/iso-50001-prep/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a iso 50001 prep with structured process, quality checks, and system integration +--- + +# Iso 50001 Prep + +## Purpose + +Create a comprehensive iso 50001 prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing iso 50001 prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the iso 50001 prep +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the iso 50001 prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Iso 50001 Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/leed-preparation/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/leed-preparation/SKILL.md new file mode 100644 index 0000000..8fdf6a3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/leed-preparation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a leed preparation with structured process, quality checks, and system integration +--- + +# Leed Preparation + +## Purpose + +Create a comprehensive leed preparation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing leed preparation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the leed preparation +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the leed preparation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Leed Preparation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/materiality-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/materiality-assessment/SKILL.md new file mode 100644 index 0000000..8ca6426 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/materiality-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a materiality assessment with structured process, quality checks, and system integration +--- + +# Materiality Assessment + +## Purpose + +Analyze and produce a comprehensive materiality assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing materiality assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the materiality assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the materiality assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Materiality Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/net-zero-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/net-zero-plan/SKILL.md new file mode 100644 index 0000000..038e892 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/net-zero-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a net zero plan with structured process, quality checks, and system integration +--- + +# Net Zero Plan + +## Purpose + +Design and document a comprehensive net zero plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing net zero plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the net zero plan +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the net zero plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Net Zero Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/permit-tracking/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/permit-tracking/SKILL.md new file mode 100644 index 0000000..2f00980 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/permit-tracking/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a permit tracking with structured process, quality checks, and system integration +--- + +# Permit Tracking + +## Purpose + +Create a comprehensive permit tracking that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing permit tracking documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the permit tracking +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the permit tracking using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Permit Tracking + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/ppa-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/ppa-analysis/SKILL.md new file mode 100644 index 0000000..31a1744 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/ppa-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a ppa analysis with structured process, quality checks, and system integration +--- + +# Ppa Analysis + +## Purpose + +Analyze and produce a comprehensive ppa analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ppa analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ppa analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ppa analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Ppa Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/recycling-program/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/recycling-program/SKILL.md new file mode 100644 index 0000000..18e8080 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/recycling-program/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a recycling program with structured process, quality checks, and system integration +--- + +# Recycling Program + +## Purpose + +Design and document a comprehensive recycling program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recycling program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recycling program +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recycling program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Recycling Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/renewable-energy-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/renewable-energy-assessment/SKILL.md new file mode 100644 index 0000000..b07197a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/renewable-energy-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a renewable energy assessment with structured process, quality checks, and system integration +--- + +# Renewable Energy Assessment + +## Purpose + +Analyze and produce a comprehensive renewable energy assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing renewable energy assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the renewable energy assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the renewable energy assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Renewable Energy Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/renewable-energy-certificate/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/renewable-energy-certificate/SKILL.md new file mode 100644 index 0000000..8488f29 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/renewable-energy-certificate/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a renewable energy certificate with structured process, quality checks, and system integration +--- + +# Renewable Energy Certificate + +## Purpose + +Create a comprehensive renewable energy certificate that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing renewable energy certificate documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the renewable energy certificate +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the renewable energy certificate using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Renewable Energy Certificate + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/resilience-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/resilience-planning/SKILL.md new file mode 100644 index 0000000..14ff7f1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/resilience-planning/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a resilience planning with structured process, quality checks, and system integration +--- + +# Resilience Planning + +## Purpose + +Design and document a comprehensive resilience planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing resilience planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the resilience planning +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the resilience planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Resilience Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/science-based-targets/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/science-based-targets/SKILL.md new file mode 100644 index 0000000..6f5c1f1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/science-based-targets/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a science based targets with structured process, quality checks, and system integration +--- + +# Science Based Targets + +## Purpose + +Create a comprehensive science based targets that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing science based targets documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the science based targets +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the science based targets using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Science Based Targets + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/scope-3-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/scope-3-analysis/SKILL.md new file mode 100644 index 0000000..51e5474 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/scope-3-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a scope 3 analysis with structured process, quality checks, and system integration +--- + +# Scope 3 Analysis + +## Purpose + +Analyze and produce a comprehensive scope 3 analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scope 3 analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scope 3 analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scope 3 analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Scope 3 Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/social-license/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/social-license/SKILL.md new file mode 100644 index 0000000..6d0ae3d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/social-license/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a social license with structured process, quality checks, and system integration +--- + +# Social License + +## Purpose + +Create a comprehensive social license that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social license documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social license +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social license using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Social License + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/solar-feasibility/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/solar-feasibility/SKILL.md new file mode 100644 index 0000000..c359099 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/solar-feasibility/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a solar feasibility with structured process, quality checks, and system integration +--- + +# Solar Feasibility + +## Purpose + +Create a comprehensive solar feasibility that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing solar feasibility documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the solar feasibility +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the solar feasibility using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Solar Feasibility + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/stakeholder-engagement-esg/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/stakeholder-engagement-esg/SKILL.md new file mode 100644 index 0000000..b16bb1a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/stakeholder-engagement-esg/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a stakeholder engagement esg with structured process, quality checks, and system integration +--- + +# Stakeholder Engagement Esg + +## Purpose + +Create a comprehensive stakeholder engagement esg that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stakeholder engagement esg documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stakeholder engagement esg +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stakeholder engagement esg using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Stakeholder Engagement Esg + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/supplier-sustainability-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/supplier-sustainability-audit/SKILL.md new file mode 100644 index 0000000..06386be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/supplier-sustainability-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a supplier sustainability audit with structured process, quality checks, and system integration +--- + +# Supplier Sustainability Audit + +## Purpose + +Analyze and produce a comprehensive supplier sustainability audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing supplier sustainability audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the supplier sustainability audit +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the supplier sustainability audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Supplier Sustainability Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/sustainability-communication/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/sustainability-communication/SKILL.md new file mode 100644 index 0000000..db210c0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/sustainability-communication/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a sustainability communication with structured process, quality checks, and system integration +--- + +# Sustainability Communication + +## Purpose + +Create a comprehensive sustainability communication that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainability communication documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainability communication +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainability communication using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Sustainability Communication + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/sustainability-report-esg/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/sustainability-report-esg/SKILL.md new file mode 100644 index 0000000..ded6184 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/sustainability-report-esg/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a sustainability report esg with structured process, quality checks, and system integration +--- + +# Sustainability Report Esg + +## Purpose + +Analyze and produce a comprehensive sustainability report esg that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainability report esg documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainability report esg +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainability report esg using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Sustainability Report Esg + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/sustainability-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/sustainability-strategy/SKILL.md new file mode 100644 index 0000000..80b7e42 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/sustainability-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a sustainability strategy with structured process, quality checks, and system integration +--- + +# Sustainability Strategy + +## Purpose + +Design and document a comprehensive sustainability strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainability strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainability strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainability strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Sustainability Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/sustainable-procurement/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/sustainable-procurement/SKILL.md new file mode 100644 index 0000000..d39a49f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/sustainable-procurement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a sustainable procurement with structured process, quality checks, and system integration +--- + +# Sustainable Procurement + +## Purpose + +Create a comprehensive sustainable procurement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainable procurement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainable procurement +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainable procurement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Sustainable Procurement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/utility-bill-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/utility-bill-analysis/SKILL.md new file mode 100644 index 0000000..08bb2a8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/utility-bill-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a utility bill analysis with structured process, quality checks, and system integration +--- + +# Utility Bill Analysis + +## Purpose + +Analyze and produce a comprehensive utility bill analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing utility bill analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the utility bill analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the utility bill analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Utility Bill Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/waste-management-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/waste-management-plan/SKILL.md new file mode 100644 index 0000000..dab5090 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/waste-management-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a waste management plan with structured process, quality checks, and system integration +--- + +# Waste Management Plan + +## Purpose + +Design and document a comprehensive waste management plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing waste management plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the waste management plan +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the waste management plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Waste Management Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/water-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/water-audit/SKILL.md new file mode 100644 index 0000000..b68d073 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/water-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a water audit with structured process, quality checks, and system integration +--- + +# Water Audit + +## Purpose + +Analyze and produce a comprehensive water audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing water audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the water audit +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the water audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Water Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/energy/water-management/SKILL.md b/clowdex-download/.claude/.claude/skills/energy/water-management/SKILL.md new file mode 100644 index 0000000..4f18e01 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/energy/water-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a water management with structured process, quality checks, and system integration +--- + +# Water Management + +## Purpose + +Create a comprehensive water management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Energy & Sustainability + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing water management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: GHG Protocol, Science-Based Targets (SBTi), TCFD Recommendations + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the water management +- Identify gaps, opportunities, and risks +- Define success metrics: Energy Use Intensity (EUI), Carbon Intensity, Renewable Energy %, Scope 1/2/3 Emissions +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the water management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Measure before managing — baseline everything + +## Output Format + +```markdown +# Water Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- GHG Protocol +- Science-Based Targets (SBTi) +- TCFD Recommendations +- ISO 50001 Energy Management +- Circular Economy Framework + +## Key Metrics +- Energy Use Intensity (EUI) +- Carbon Intensity +- Renewable Energy % +- Scope 1/2/3 Emissions +- Energy Cost Savings +- Waste Diversion Rate + +## Best Practices +- Measure before managing — baseline everything +- Low-cost behavioral changes before capital projects +- Prioritize Scope 1 and 2 reductions first +- Verify claims with third-party audits +- Report transparently — including Scope 3 + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/acquisition-due-diligence/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/acquisition-due-diligence/SKILL.md new file mode 100644 index 0000000..8f60c34 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/acquisition-due-diligence/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a acquisition due diligence with structured process, quality checks, and system integration +--- + +# Acquisition Due Diligence + +## Purpose + +Create a comprehensive acquisition due diligence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing acquisition due diligence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the acquisition due diligence +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the acquisition due diligence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Acquisition Due Diligence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/balance-sheet-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/balance-sheet-analysis/SKILL.md new file mode 100644 index 0000000..ee9049f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/balance-sheet-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a balance sheet analysis with structured process, quality checks, and system integration +--- + +# Balance Sheet Analysis + +## Purpose + +Analyze and produce a comprehensive balance sheet analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing balance sheet analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the balance sheet analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the balance sheet analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Balance Sheet Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/board-financial-report/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/board-financial-report/SKILL.md new file mode 100644 index 0000000..e4e800f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/board-financial-report/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a board financial report with structured process, quality checks, and system integration +--- + +# Board Financial Report + +## Purpose + +Analyze and produce a comprehensive board financial report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board financial report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board financial report +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board financial report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Board Financial Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/bonus-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/bonus-structure/SKILL.md new file mode 100644 index 0000000..986efb0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/bonus-structure/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a bonus structure with structured process, quality checks, and system integration +--- + +# Bonus Structure + +## Purpose + +Create a comprehensive bonus structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bonus structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bonus structure +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bonus structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Bonus Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/break-even-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/break-even-analysis/SKILL.md new file mode 100644 index 0000000..7b93be7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/break-even-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a break even analysis with structured process, quality checks, and system integration +--- + +# Break Even Analysis + +## Purpose + +Analyze and produce a comprehensive break even analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing break even analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the break even analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the break even analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Break Even Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/budget-template/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/budget-template/SKILL.md new file mode 100644 index 0000000..ac2745f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/budget-template/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a budget template with structured process, quality checks, and system integration +--- + +# Budget Template + +## Purpose + +Create a comprehensive budget template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing budget template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the budget template +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the budget template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Budget Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/budget-variance-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/budget-variance-analysis/SKILL.md new file mode 100644 index 0000000..dcf7bd8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/budget-variance-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a budget variance analysis with structured process, quality checks, and system integration +--- + +# Budget Variance Analysis + +## Purpose + +Analyze and produce a comprehensive budget variance analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing budget variance analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the budget variance analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the budget variance analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Budget Variance Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/cap-table/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/cap-table/SKILL.md new file mode 100644 index 0000000..b347884 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/cap-table/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a cap table with structured process, quality checks, and system integration +--- + +# Cap Table + +## Purpose + +Create a comprehensive cap table that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cap table documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cap table +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cap table using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Cap Table + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/cash-flow-forecast/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/cash-flow-forecast/SKILL.md new file mode 100644 index 0000000..352581f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/cash-flow-forecast/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a cash flow forecast with structured process, quality checks, and system integration +--- + +# Cash Flow Forecast + +## Purpose + +Analyze and produce a comprehensive cash flow forecast that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cash flow forecast documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cash flow forecast +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cash flow forecast using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Cash Flow Forecast + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/cash-flow-statement/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/cash-flow-statement/SKILL.md new file mode 100644 index 0000000..11d1184 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/cash-flow-statement/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a cash flow statement with structured process, quality checks, and system integration +--- + +# Cash Flow Statement + +## Purpose + +Create a comprehensive cash flow statement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cash flow statement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cash flow statement +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cash flow statement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Cash Flow Statement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/collections-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/collections-strategy/SKILL.md new file mode 100644 index 0000000..f18660c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/collections-strategy/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a collections strategy with structured process, quality checks, and system integration +--- + +# Collections Strategy + +## Purpose + +Design and document a comprehensive collections strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing collections strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the collections strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the collections strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Collections Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/compensation-benchmarking/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/compensation-benchmarking/SKILL.md new file mode 100644 index 0000000..0262fb5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/compensation-benchmarking/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a compensation benchmarking with structured process, quality checks, and system integration +--- + +# Compensation Benchmarking + +## Purpose + +Analyze and produce a comprehensive compensation benchmarking that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compensation benchmarking documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compensation benchmarking +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compensation benchmarking using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Compensation Benchmarking + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/competitive-pricing-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/competitive-pricing-analysis/SKILL.md new file mode 100644 index 0000000..557ac2b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/competitive-pricing-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a competitive pricing analysis with structured process, quality checks, and system integration +--- + +# Competitive Pricing Analysis + +## Purpose + +Analyze and produce a comprehensive competitive pricing analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitive pricing analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitive pricing analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitive pricing analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Competitive Pricing Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/compliance-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/compliance-checklist/SKILL.md new file mode 100644 index 0000000..150a58e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/compliance-checklist/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a compliance checklist with structured process, quality checks, and system integration +--- + +# Compliance Checklist + +## Purpose + +Analyze and produce a comprehensive compliance checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Compliance Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/cost-benefit-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/cost-benefit-analysis/SKILL.md new file mode 100644 index 0000000..5ff4130 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/cost-benefit-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a cost benefit analysis with structured process, quality checks, and system integration +--- + +# Cost Benefit Analysis + +## Purpose + +Analyze and produce a comprehensive cost benefit analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost benefit analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost benefit analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost benefit analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Cost Benefit Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/cost-reduction-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/cost-reduction-plan/SKILL.md new file mode 100644 index 0000000..c6acab5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/cost-reduction-plan/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a cost reduction plan with structured process, quality checks, and system integration +--- + +# Cost Reduction Plan + +## Purpose + +Design and document a comprehensive cost reduction plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost reduction plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost reduction plan +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost reduction plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Cost Reduction Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/dcf-valuation/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/dcf-valuation/SKILL.md new file mode 100644 index 0000000..abf84c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/dcf-valuation/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a dcf valuation with structured process, quality checks, and system integration +--- + +# Dcf Valuation + +## Purpose + +Create a comprehensive dcf valuation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dcf valuation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dcf valuation +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dcf valuation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Dcf Valuation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/deduction-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/deduction-tracker/SKILL.md new file mode 100644 index 0000000..2905d12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/deduction-tracker/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a deduction tracker with structured process, quality checks, and system integration +--- + +# Deduction Tracker + +## Purpose + +Analyze and produce a comprehensive deduction tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deduction tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deduction tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deduction tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Deduction Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/deferred-revenue-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/deferred-revenue-schedule/SKILL.md new file mode 100644 index 0000000..3db8471 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/deferred-revenue-schedule/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a deferred revenue schedule with structured process, quality checks, and system integration +--- + +# Deferred Revenue Schedule + +## Purpose + +Design and document a comprehensive deferred revenue schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deferred revenue schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deferred revenue schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deferred revenue schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Deferred Revenue Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/depreciation-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/depreciation-schedule/SKILL.md new file mode 100644 index 0000000..73b9e57 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/depreciation-schedule/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a depreciation schedule with structured process, quality checks, and system integration +--- + +# Depreciation Schedule + +## Purpose + +Design and document a comprehensive depreciation schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing depreciation schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the depreciation schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the depreciation schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Depreciation Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/expense-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/expense-policy/SKILL.md new file mode 100644 index 0000000..da5eb51 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/expense-policy/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a expense policy with structured process, quality checks, and system integration +--- + +# Expense Policy + +## Purpose + +Create a comprehensive expense policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing expense policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the expense policy +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the expense policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Expense Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/expense-report-template/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/expense-report-template/SKILL.md new file mode 100644 index 0000000..bdaabac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/expense-report-template/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a expense report template with structured process, quality checks, and system integration +--- + +# Expense Report Template + +## Purpose + +Analyze and produce a comprehensive expense report template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing expense report template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the expense report template +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the expense report template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Expense Report Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/financial-audit-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/financial-audit-prep/SKILL.md new file mode 100644 index 0000000..b79bc2f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/financial-audit-prep/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a financial audit prep with structured process, quality checks, and system integration +--- + +# Financial Audit Prep + +## Purpose + +Analyze and produce a comprehensive financial audit prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing financial audit prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the financial audit prep +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the financial audit prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Financial Audit Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/financial-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/financial-dashboard/SKILL.md new file mode 100644 index 0000000..8ec447b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/financial-dashboard/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a financial dashboard with structured process, quality checks, and system integration +--- + +# Financial Dashboard + +## Purpose + +Analyze and produce a comprehensive financial dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing financial dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the financial dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the financial dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Financial Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/financial-model/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/financial-model/SKILL.md new file mode 100644 index 0000000..4eb6da1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/financial-model/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a financial model with structured process, quality checks, and system integration +--- + +# Financial Model + +## Purpose + +Design and document a comprehensive financial model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing financial model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the financial model +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the financial model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Financial Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/financial-ratio-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/financial-ratio-analysis/SKILL.md new file mode 100644 index 0000000..bdbd7ee --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/financial-ratio-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a financial ratio analysis with structured process, quality checks, and system integration +--- + +# Financial Ratio Analysis + +## Purpose + +Analyze and produce a comprehensive financial ratio analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing financial ratio analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the financial ratio analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the financial ratio analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Financial Ratio Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/fundraising-financial-model/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/fundraising-financial-model/SKILL.md new file mode 100644 index 0000000..88ed862 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/fundraising-financial-model/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a fundraising financial model with structured process, quality checks, and system integration +--- + +# Fundraising Financial Model + +## Purpose + +Design and document a comprehensive fundraising financial model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fundraising financial model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fundraising financial model +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fundraising financial model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Fundraising Financial Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/internal-controls/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/internal-controls/SKILL.md new file mode 100644 index 0000000..742dd9a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/internal-controls/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a internal controls with structured process, quality checks, and system integration +--- + +# Internal Controls + +## Purpose + +Create a comprehensive internal controls that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing internal controls documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the internal controls +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the internal controls using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Internal Controls + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/inventory-valuation/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/inventory-valuation/SKILL.md new file mode 100644 index 0000000..cc74857 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/inventory-valuation/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a inventory valuation with structured process, quality checks, and system integration +--- + +# Inventory Valuation + +## Purpose + +Create a comprehensive inventory valuation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inventory valuation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inventory valuation +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inventory valuation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Inventory Valuation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/investor-report/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/investor-report/SKILL.md new file mode 100644 index 0000000..db988fc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/investor-report/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a investor report with structured process, quality checks, and system integration +--- + +# Investor Report + +## Purpose + +Analyze and produce a comprehensive investor report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor report +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Investor Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/invoice-template/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/invoice-template/SKILL.md new file mode 100644 index 0000000..01824b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/invoice-template/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a invoice template with structured process, quality checks, and system integration +--- + +# Invoice Template + +## Purpose + +Create a comprehensive invoice template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing invoice template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the invoice template +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the invoice template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Invoice Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/kpi-scorecard/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/kpi-scorecard/SKILL.md new file mode 100644 index 0000000..0aad7c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/kpi-scorecard/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a kpi scorecard with structured process, quality checks, and system integration +--- + +# Kpi Scorecard + +## Purpose + +Analyze and produce a comprehensive kpi scorecard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kpi scorecard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kpi scorecard +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kpi scorecard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Kpi Scorecard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/management-report/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/management-report/SKILL.md new file mode 100644 index 0000000..1906f8d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/management-report/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a management report with structured process, quality checks, and system integration +--- + +# Management Report + +## Purpose + +Analyze and produce a comprehensive management report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing management report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the management report +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the management report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Management Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/merger-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/merger-analysis/SKILL.md new file mode 100644 index 0000000..2e8ac44 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/merger-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a merger analysis with structured process, quality checks, and system integration +--- + +# Merger Analysis + +## Purpose + +Analyze and produce a comprehensive merger analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing merger analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the merger analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the merger analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Merger Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/monte-carlo-simulation/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/monte-carlo-simulation/SKILL.md new file mode 100644 index 0000000..5efe25a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/monte-carlo-simulation/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a monte carlo simulation with structured process, quality checks, and system integration +--- + +# Monte Carlo Simulation + +## Purpose + +Create a comprehensive monte carlo simulation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing monte carlo simulation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the monte carlo simulation +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the monte carlo simulation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Monte Carlo Simulation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/mrr-arr-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/mrr-arr-calculator/SKILL.md new file mode 100644 index 0000000..dd9d4e9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/mrr-arr-calculator/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a mrr arr calculator with structured process, quality checks, and system integration +--- + +# Mrr Arr Calculator + +## Purpose + +Create a comprehensive mrr arr calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mrr arr calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mrr arr calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mrr arr calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Mrr Arr Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/npv-irr-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/npv-irr-analysis/SKILL.md new file mode 100644 index 0000000..e2235b3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/npv-irr-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a npv irr analysis with structured process, quality checks, and system integration +--- + +# Npv Irr Analysis + +## Purpose + +Analyze and produce a comprehensive npv irr analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing npv irr analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the npv irr analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the npv irr analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Npv Irr Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/payback-period-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/payback-period-analysis/SKILL.md new file mode 100644 index 0000000..9fa8e9f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/payback-period-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a payback period analysis with structured process, quality checks, and system integration +--- + +# Payback Period Analysis + +## Purpose + +Analyze and produce a comprehensive payback period analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing payback period analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the payback period analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the payback period analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Payback Period Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/payment-terms/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/payment-terms/SKILL.md new file mode 100644 index 0000000..48850f5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/payment-terms/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a payment terms with structured process, quality checks, and system integration +--- + +# Payment Terms + +## Purpose + +Create a comprehensive payment terms that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing payment terms documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the payment terms +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the payment terms using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Payment Terms + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/price-sensitivity-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/price-sensitivity-analysis/SKILL.md new file mode 100644 index 0000000..829dfc5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/price-sensitivity-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a price sensitivity analysis with structured process, quality checks, and system integration +--- + +# Price Sensitivity Analysis + +## Purpose + +Analyze and produce a comprehensive price sensitivity analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing price sensitivity analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the price sensitivity analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the price sensitivity analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Price Sensitivity Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/pricing-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/pricing-strategy/SKILL.md new file mode 100644 index 0000000..1dfe320 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/pricing-strategy/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a pricing strategy with structured process, quality checks, and system integration +--- + +# Pricing Strategy + +## Purpose + +Design and document a comprehensive pricing strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Pricing Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/procurement-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/procurement-policy/SKILL.md new file mode 100644 index 0000000..a489a7d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/procurement-policy/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a procurement policy with structured process, quality checks, and system integration +--- + +# Procurement Policy + +## Purpose + +Create a comprehensive procurement policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing procurement policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the procurement policy +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the procurement policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Procurement Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/profit-loss-statement/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/profit-loss-statement/SKILL.md new file mode 100644 index 0000000..52f1f8e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/profit-loss-statement/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a profit loss statement with structured process, quality checks, and system integration +--- + +# Profit Loss Statement + +## Purpose + +Create a comprehensive profit loss statement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing profit loss statement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the profit loss statement +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the profit loss statement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Profit Loss Statement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/quarterly-financial-review/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/quarterly-financial-review/SKILL.md new file mode 100644 index 0000000..3b47cbc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/quarterly-financial-review/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a quarterly financial review with structured process, quality checks, and system integration +--- + +# Quarterly Financial Review + +## Purpose + +Analyze and produce a comprehensive quarterly financial review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quarterly financial review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quarterly financial review +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quarterly financial review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Quarterly Financial Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/quarterly-tax-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/quarterly-tax-prep/SKILL.md new file mode 100644 index 0000000..b3a8cea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/quarterly-tax-prep/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a quarterly tax prep with structured process, quality checks, and system integration +--- + +# Quarterly Tax Prep + +## Purpose + +Create a comprehensive quarterly tax prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quarterly tax prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quarterly tax prep +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quarterly tax prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Quarterly Tax Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/revenue-model/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/revenue-model/SKILL.md new file mode 100644 index 0000000..c8d66e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/revenue-model/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a revenue model with structured process, quality checks, and system integration +--- + +# Revenue Model + +## Purpose + +Design and document a comprehensive revenue model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing revenue model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the revenue model +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the revenue model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Revenue Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/revenue-recognition/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/revenue-recognition/SKILL.md new file mode 100644 index 0000000..5810c34 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/revenue-recognition/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a revenue recognition with structured process, quality checks, and system integration +--- + +# Revenue Recognition + +## Purpose + +Create a comprehensive revenue recognition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing revenue recognition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the revenue recognition +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the revenue recognition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Revenue Recognition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/roi-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/roi-analysis/SKILL.md new file mode 100644 index 0000000..3879c9a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/roi-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a roi analysis with structured process, quality checks, and system integration +--- + +# Roi Analysis + +## Purpose + +Analyze and produce a comprehensive roi analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing roi analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the roi analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the roi analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Roi Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/runway-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/runway-calculator/SKILL.md new file mode 100644 index 0000000..225b3cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/runway-calculator/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a runway calculator with structured process, quality checks, and system integration +--- + +# Runway Calculator + +## Purpose + +Create a comprehensive runway calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing runway calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the runway calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the runway calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Runway Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/salary-band-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/salary-band-structure/SKILL.md new file mode 100644 index 0000000..db7df52 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/salary-band-structure/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a salary band structure with structured process, quality checks, and system integration +--- + +# Salary Band Structure + +## Purpose + +Create a comprehensive salary band structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing salary band structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the salary band structure +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the salary band structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Salary Band Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/scenario-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/scenario-planning/SKILL.md new file mode 100644 index 0000000..144d513 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/scenario-planning/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a scenario planning with structured process, quality checks, and system integration +--- + +# Scenario Planning + +## Purpose + +Design and document a comprehensive scenario planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing scenario planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the scenario planning +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the scenario planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Scenario Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/sensitivity-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/sensitivity-analysis/SKILL.md new file mode 100644 index 0000000..5afa7f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/sensitivity-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a sensitivity analysis with structured process, quality checks, and system integration +--- + +# Sensitivity Analysis + +## Purpose + +Analyze and produce a comprehensive sensitivity analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sensitivity analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sensitivity analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sensitivity analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Sensitivity Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/subscription-cost-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/subscription-cost-audit/SKILL.md new file mode 100644 index 0000000..2ffd29a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/subscription-cost-audit/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a subscription cost audit with structured process, quality checks, and system integration +--- + +# Subscription Cost Audit + +## Purpose + +Analyze and produce a comprehensive subscription cost audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subscription cost audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subscription cost audit +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subscription cost audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Subscription Cost Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/synergy-model/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/synergy-model/SKILL.md new file mode 100644 index 0000000..8dc679e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/synergy-model/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a synergy model with structured process, quality checks, and system integration +--- + +# Synergy Model + +## Purpose + +Design and document a comprehensive synergy model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing synergy model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the synergy model +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the synergy model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Synergy Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/tax-planning-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/tax-planning-checklist/SKILL.md new file mode 100644 index 0000000..c930c39 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/tax-planning-checklist/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a tax planning checklist with structured process, quality checks, and system integration +--- + +# Tax Planning Checklist + +## Purpose + +Analyze and produce a comprehensive tax planning checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tax planning checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tax planning checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tax planning checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Tax Planning Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/term-sheet-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/term-sheet-analysis/SKILL.md new file mode 100644 index 0000000..709f143 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/term-sheet-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a term sheet analysis with structured process, quality checks, and system integration +--- + +# Term Sheet Analysis + +## Purpose + +Analyze and produce a comprehensive term sheet analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing term sheet analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the term sheet analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the term sheet analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Term Sheet Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/unit-economics-model/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/unit-economics-model/SKILL.md new file mode 100644 index 0000000..def6978 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/unit-economics-model/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Design and document a unit economics model with structured process, quality checks, and system integration +--- + +# Unit Economics Model + +## Purpose + +Design and document a comprehensive unit economics model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing unit economics model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the unit economics model +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the unit economics model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Unit Economics Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/vendor-payment-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/vendor-payment-analysis/SKILL.md new file mode 100644 index 0000000..cc59294 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/vendor-payment-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a vendor payment analysis with structured process, quality checks, and system integration +--- + +# Vendor Payment Analysis + +## Purpose + +Analyze and produce a comprehensive vendor payment analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor payment analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor payment analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor payment analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Vendor Payment Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/working-capital-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/working-capital-analysis/SKILL.md new file mode 100644 index 0000000..343d2af --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/working-capital-analysis/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Analyze and produce a working capital analysis with structured process, quality checks, and system integration +--- + +# Working Capital Analysis + +## Purpose + +Analyze and produce a comprehensive working capital analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing working capital analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the working capital analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the working capital analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Working Capital Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/finance/zero-based-budget/SKILL.md b/clowdex-download/.claude/.claude/skills/finance/zero-based-budget/SKILL.md new file mode 100644 index 0000000..cc5054c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/finance/zero-based-budget/SKILL.md @@ -0,0 +1,136 @@ +--- +description: Create a zero based budget with structured process, quality checks, and system integration +--- + +# Zero Based Budget + +## Purpose + +Create a comprehensive zero based budget that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Finance & Accounting + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Time Period**: The timeframe for analysis or projection + +### Optional +- **Historical Data**: Previous period data for comparison +- **Assumptions**: Key assumptions to use in calculations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing zero based budget documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Three Statement Model, DCF Valuation, Comparable Company Analysis + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the zero based budget +- Identify gaps, opportunities, and risks +- Define success metrics: Gross Margin, Net Margin, EBITDA, Burn Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the zero based budget using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Never build a model without clearly stating assumptions + +## Output Format + +```markdown +# Zero Based Budget + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Three Statement Model +- DCF Valuation +- Comparable Company Analysis +- Zero-Based Budgeting +- Rolling Forecast +- Scenario Planning (Bull/Base/Bear) +- Unit Economics + +## Key Metrics +- Gross Margin +- Net Margin +- EBITDA +- Burn Rate +- Runway +- CAC Payback Period +- Rule of 40 +- Current Ratio +- Quick Ratio + +## Best Practices +- Never build a model without clearly stating assumptions +- Separate inputs from calculations from outputs +- Use sensitivity analysis on top 3 variables +- Monthly close within 5 business days +- Forecast accuracy within 10% of actuals + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/app-programming/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/app-programming/SKILL.md new file mode 100644 index 0000000..ccf4be7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/app-programming/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a app programming with structured process, quality checks, and system integration +--- + +# App Programming + +## Purpose + +Design and document a comprehensive app programming that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing app programming documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the app programming +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the app programming using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# App Programming + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/body-composition-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/body-composition-analysis/SKILL.md new file mode 100644 index 0000000..ef8adaa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/body-composition-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a body composition analysis with structured process, quality checks, and system integration +--- + +# Body Composition Analysis + +## Purpose + +Analyze and produce a comprehensive body composition analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing body composition analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the body composition analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the body composition analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Body Composition Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/bootcamp-program/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/bootcamp-program/SKILL.md new file mode 100644 index 0000000..fe7c4d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/bootcamp-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a bootcamp program with structured process, quality checks, and system integration +--- + +# Bootcamp Program + +## Purpose + +Design and document a comprehensive bootcamp program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bootcamp program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bootcamp program +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bootcamp program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Bootcamp Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/breathwork-session/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/breathwork-session/SKILL.md new file mode 100644 index 0000000..ebb6334 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/breathwork-session/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a breathwork session with structured process, quality checks, and system integration +--- + +# Breathwork Session + +## Purpose + +Create a comprehensive breathwork session that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breathwork session documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breathwork session +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breathwork session using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Breathwork Session + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/certification-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/certification-prep/SKILL.md new file mode 100644 index 0000000..389be44 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/certification-prep/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a certification prep with structured process, quality checks, and system integration +--- + +# Certification Prep + +## Purpose + +Create a comprehensive certification prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing certification prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the certification prep +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the certification prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Certification Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/class-design/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/class-design/SKILL.md new file mode 100644 index 0000000..799eb28 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/class-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a class design with structured process, quality checks, and system integration +--- + +# Class Design + +## Purpose + +Create a comprehensive class design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing class design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the class design +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the class design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Class Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/cleaning-protocol/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/cleaning-protocol/SKILL.md new file mode 100644 index 0000000..4e12baf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/cleaning-protocol/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cleaning protocol with structured process, quality checks, and system integration +--- + +# Cleaning Protocol + +## Purpose + +Create a comprehensive cleaning protocol that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cleaning protocol documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cleaning protocol +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cleaning protocol using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Cleaning Protocol + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/client-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-assessment/SKILL.md new file mode 100644 index 0000000..e98860c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a client assessment with structured process, quality checks, and system integration +--- + +# Client Assessment + +## Purpose + +Analyze and produce a comprehensive client assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Client Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/client-onboarding-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-onboarding-fitness/SKILL.md new file mode 100644 index 0000000..ce93cab --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-onboarding-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a client onboarding fitness with structured process, quality checks, and system integration +--- + +# Client Onboarding Fitness + +## Purpose + +Create a comprehensive client onboarding fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client onboarding fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client onboarding fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client onboarding fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Client Onboarding Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/client-retention-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-retention-fitness/SKILL.md new file mode 100644 index 0000000..1d9690d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/client-retention-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a client retention fitness with structured process, quality checks, and system integration +--- + +# Client Retention Fitness + +## Purpose + +Create a comprehensive client retention fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing client retention fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the client retention fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the client retention fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Client Retention Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/content-plan-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/content-plan-fitness/SKILL.md new file mode 100644 index 0000000..29aa510 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/content-plan-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a content plan fitness with structured process, quality checks, and system integration +--- + +# Content Plan Fitness + +## Purpose + +Design and document a comprehensive content plan fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content plan fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content plan fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content plan fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Content Plan Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/continuing-education-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/continuing-education-plan/SKILL.md new file mode 100644 index 0000000..f1a42fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/continuing-education-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a continuing education plan with structured process, quality checks, and system integration +--- + +# Continuing Education Plan + +## Purpose + +Design and document a comprehensive continuing education plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing continuing education plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the continuing education plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the continuing education plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Continuing Education Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/corporate-wellness-program/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/corporate-wellness-program/SKILL.md new file mode 100644 index 0000000..d778cec --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/corporate-wellness-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a corporate wellness program with structured process, quality checks, and system integration +--- + +# Corporate Wellness Program + +## Purpose + +Design and document a comprehensive corporate wellness program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate wellness program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate wellness program +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate wellness program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Corporate Wellness Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/equipment-maintenance-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/equipment-maintenance-fitness/SKILL.md new file mode 100644 index 0000000..f055593 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/equipment-maintenance-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a equipment maintenance fitness with structured process, quality checks, and system integration +--- + +# Equipment Maintenance Fitness + +## Purpose + +Create a comprehensive equipment maintenance fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing equipment maintenance fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the equipment maintenance fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the equipment maintenance fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Equipment Maintenance Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-business-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-business-plan/SKILL.md new file mode 100644 index 0000000..9c5f44c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-business-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a fitness business plan with structured process, quality checks, and system integration +--- + +# Fitness Business Plan + +## Purpose + +Design and document a comprehensive fitness business plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fitness business plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fitness business plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fitness business plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Fitness Business Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-test/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-test/SKILL.md new file mode 100644 index 0000000..40a42e2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/fitness-test/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a fitness test with structured process, quality checks, and system integration +--- + +# Fitness Test + +## Purpose + +Create a comprehensive fitness test that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fitness test documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fitness test +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fitness test using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Fitness Test + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/goal-setting-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/goal-setting-fitness/SKILL.md new file mode 100644 index 0000000..166dd89 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/goal-setting-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a goal setting fitness with structured process, quality checks, and system integration +--- + +# Goal Setting Fitness + +## Purpose + +Create a comprehensive goal setting fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing goal setting fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the goal setting fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the goal setting fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Goal Setting Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/group-fitness-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/group-fitness-plan/SKILL.md new file mode 100644 index 0000000..17766ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/group-fitness-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a group fitness plan with structured process, quality checks, and system integration +--- + +# Group Fitness Plan + +## Purpose + +Design and document a comprehensive group fitness plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing group fitness plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the group fitness plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the group fitness plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Group Fitness Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/habit-change-program/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/habit-change-program/SKILL.md new file mode 100644 index 0000000..6ae7da4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/habit-change-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a habit change program with structured process, quality checks, and system integration +--- + +# Habit Change Program + +## Purpose + +Design and document a comprehensive habit change program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing habit change program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the habit change program +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the habit change program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Habit Change Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/injury-prevention/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/injury-prevention/SKILL.md new file mode 100644 index 0000000..31b27f7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/injury-prevention/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a injury prevention with structured process, quality checks, and system integration +--- + +# Injury Prevention + +## Purpose + +Create a comprehensive injury prevention that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing injury prevention documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the injury prevention +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the injury prevention using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Injury Prevention + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/meal-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/meal-plan/SKILL.md new file mode 100644 index 0000000..af93799 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/meal-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a meal plan with structured process, quality checks, and system integration +--- + +# Meal Plan + +## Purpose + +Design and document a comprehensive meal plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meal plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meal plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meal plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Meal Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/meditation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/meditation-guide/SKILL.md new file mode 100644 index 0000000..411156a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/meditation-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a meditation guide with structured process, quality checks, and system integration +--- + +# Meditation Guide + +## Purpose + +Design and document a comprehensive meditation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meditation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meditation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meditation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Meditation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/membership-model/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/membership-model/SKILL.md new file mode 100644 index 0000000..383942d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/membership-model/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a membership model with structured process, quality checks, and system integration +--- + +# Membership Model + +## Purpose + +Design and document a comprehensive membership model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing membership model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the membership model +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the membership model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Membership Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/nutrition-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/nutrition-plan/SKILL.md new file mode 100644 index 0000000..5dbacf7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/nutrition-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a nutrition plan with structured process, quality checks, and system integration +--- + +# Nutrition Plan + +## Purpose + +Design and document a comprehensive nutrition plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nutrition plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nutrition plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nutrition plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Nutrition Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/online-coaching-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/online-coaching-setup/SKILL.md new file mode 100644 index 0000000..be44cfb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/online-coaching-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a online coaching setup with structured process, quality checks, and system integration +--- + +# Online Coaching Setup + +## Purpose + +Design and document a comprehensive online coaching setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing online coaching setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the online coaching setup +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the online coaching setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Online Coaching Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/periodization-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/periodization-plan/SKILL.md new file mode 100644 index 0000000..d99e0aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/periodization-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a periodization plan with structured process, quality checks, and system integration +--- + +# Periodization Plan + +## Purpose + +Design and document a comprehensive periodization plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing periodization plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the periodization plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the periodization plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Periodization Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/pricing-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/pricing-fitness/SKILL.md new file mode 100644 index 0000000..f97f57d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/pricing-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a pricing fitness with structured process, quality checks, and system integration +--- + +# Pricing Fitness + +## Purpose + +Create a comprehensive pricing fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Pricing Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/progress-tracking/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/progress-tracking/SKILL.md new file mode 100644 index 0000000..e0de840 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/progress-tracking/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a progress tracking with structured process, quality checks, and system integration +--- + +# Progress Tracking + +## Purpose + +Create a comprehensive progress tracking that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing progress tracking documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the progress tracking +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the progress tracking using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Progress Tracking + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/referral-program-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/referral-program-fitness/SKILL.md new file mode 100644 index 0000000..9d428ef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/referral-program-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a referral program fitness with structured process, quality checks, and system integration +--- + +# Referral Program Fitness + +## Purpose + +Design and document a comprehensive referral program fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral program fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral program fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral program fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Referral Program Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/rehab-protocol-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/rehab-protocol-guide/SKILL.md new file mode 100644 index 0000000..5c6f552 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/rehab-protocol-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a rehab protocol guide with structured process, quality checks, and system integration +--- + +# Rehab Protocol Guide + +## Purpose + +Design and document a comprehensive rehab protocol guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rehab protocol guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rehab protocol guide +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rehab protocol guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Rehab Protocol Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/retreat-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/retreat-planning/SKILL.md new file mode 100644 index 0000000..0327d20 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/retreat-planning/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a retreat planning with structured process, quality checks, and system integration +--- + +# Retreat Planning + +## Purpose + +Design and document a comprehensive retreat planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retreat planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retreat planning +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retreat planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Retreat Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/return-to-sport/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/return-to-sport/SKILL.md new file mode 100644 index 0000000..20bcfa9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/return-to-sport/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a return to sport with structured process, quality checks, and system integration +--- + +# Return To Sport + +## Purpose + +Create a comprehensive return to sport that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing return to sport documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the return to sport +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the return to sport using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Return To Sport + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/social-media-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/social-media-fitness/SKILL.md new file mode 100644 index 0000000..bf81185 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/social-media-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a social media fitness with structured process, quality checks, and system integration +--- + +# Social Media Fitness + +## Purpose + +Create a comprehensive social media fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Social Media Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/specialization-track/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/specialization-track/SKILL.md new file mode 100644 index 0000000..a5aac6f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/specialization-track/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a specialization track with structured process, quality checks, and system integration +--- + +# Specialization Track + +## Purpose + +Create a comprehensive specialization track that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing specialization track documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the specialization track +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the specialization track using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Specialization Track + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/stress-management/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/stress-management/SKILL.md new file mode 100644 index 0000000..a0b559d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/stress-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a stress management with structured process, quality checks, and system integration +--- + +# Stress Management + +## Purpose + +Create a comprehensive stress management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stress management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stress management +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stress management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Stress Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/studio-operations/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/studio-operations/SKILL.md new file mode 100644 index 0000000..e35df0d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/studio-operations/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a studio operations with structured process, quality checks, and system integration +--- + +# Studio Operations + +## Purpose + +Create a comprehensive studio operations that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing studio operations documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the studio operations +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the studio operations using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Studio Operations + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/supplement-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/supplement-guide/SKILL.md new file mode 100644 index 0000000..0e16a92 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/supplement-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a supplement guide with structured process, quality checks, and system integration +--- + +# Supplement Guide + +## Purpose + +Design and document a comprehensive supplement guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing supplement guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the supplement guide +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the supplement guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Supplement Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/testimonial-collection/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/testimonial-collection/SKILL.md new file mode 100644 index 0000000..66180f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/testimonial-collection/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a testimonial collection with structured process, quality checks, and system integration +--- + +# Testimonial Collection + +## Purpose + +Create a comprehensive testimonial collection that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing testimonial collection documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the testimonial collection +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the testimonial collection using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Testimonial Collection + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/training-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/training-plan/SKILL.md new file mode 100644 index 0000000..dfc26d9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/training-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a training plan with structured process, quality checks, and system integration +--- + +# Training Plan + +## Purpose + +Design and document a comprehensive training plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing training plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the training plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the training plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Training Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/transformation-story/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/transformation-story/SKILL.md new file mode 100644 index 0000000..8c27915 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/transformation-story/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a transformation story with structured process, quality checks, and system integration +--- + +# Transformation Story + +## Purpose + +Create a comprehensive transformation story that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing transformation story documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the transformation story +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the transformation story using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Transformation Story + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/virtual-training-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/virtual-training-guide/SKILL.md new file mode 100644 index 0000000..17bdcbb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/virtual-training-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a virtual training guide with structured process, quality checks, and system integration +--- + +# Virtual Training Guide + +## Purpose + +Design and document a comprehensive virtual training guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing virtual training guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the virtual training guide +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the virtual training guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Virtual Training Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/wellness-coaching-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/wellness-coaching-plan/SKILL.md new file mode 100644 index 0000000..d13bfef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/wellness-coaching-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a wellness coaching plan with structured process, quality checks, and system integration +--- + +# Wellness Coaching Plan + +## Purpose + +Design and document a comprehensive wellness coaching plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wellness coaching plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wellness coaching plan +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wellness coaching plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Wellness Coaching Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/workout-program/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/workout-program/SKILL.md new file mode 100644 index 0000000..b934fdb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/workout-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a workout program with structured process, quality checks, and system integration +--- + +# Workout Program + +## Purpose + +Design and document a comprehensive workout program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workout program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workout program +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workout program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Workout Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/workshop-fitness/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/workshop-fitness/SKILL.md new file mode 100644 index 0000000..40f0666 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/workshop-fitness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a workshop fitness with structured process, quality checks, and system integration +--- + +# Workshop Fitness + +## Purpose + +Create a comprehensive workshop fitness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workshop fitness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workshop fitness +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workshop fitness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Workshop Fitness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/fitness-wellness/yoga-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/fitness-wellness/yoga-sequence/SKILL.md new file mode 100644 index 0000000..b7d2482 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/fitness-wellness/yoga-sequence/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a yoga sequence with structured process, quality checks, and system integration +--- + +# Yoga Sequence + +## Purpose + +Create a comprehensive yoga sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Fitness & Wellness + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing yoga sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Periodization, Progressive Overload, Behavior Change Model (Transtheoretical) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the yoga sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Client Retention Rate, Session Attendance Rate, Client Goal Achievement, Revenue Per Client +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the yoga sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Initial assessment before programming + +## Output Format + +```markdown +# Yoga Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Periodization +- Progressive Overload +- Behavior Change Model (Transtheoretical) +- Motivational Interviewing +- Biopsychosocial Model + +## Key Metrics +- Client Retention Rate +- Session Attendance Rate +- Client Goal Achievement +- Revenue Per Client +- Referral Rate +- Client Satisfaction Score + +## Best Practices +- Initial assessment before programming +- Reassess every 4-6 weeks +- Track adherence, not just results +- Communication between sessions (check-ins) +- Scope of practice — refer out when appropriate +- DISCLAIMER: Skills provide fitness programming frameworks — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/allergen-management/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/allergen-management/SKILL.md new file mode 100644 index 0000000..5525db0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/allergen-management/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a allergen management with structured process, quality checks, and system integration +--- + +# Allergen Management + +## Purpose + +Create a comprehensive allergen management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing allergen management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the allergen management +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the allergen management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Allergen Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/bar-training/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/bar-training/SKILL.md new file mode 100644 index 0000000..07609d0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/bar-training/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a bar training with structured process, quality checks, and system integration +--- + +# Bar Training + +## Purpose + +Create a comprehensive bar training that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bar training documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bar training +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bar training using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Bar Training + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/brand-standards/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/brand-standards/SKILL.md new file mode 100644 index 0000000..20743a5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/brand-standards/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a brand standards with structured process, quality checks, and system integration +--- + +# Brand Standards + +## Purpose + +Create a comprehensive brand standards that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand standards documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand standards +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand standards using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Brand Standards + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/catering-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/catering-proposal/SKILL.md new file mode 100644 index 0000000..f6ffd4c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/catering-proposal/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a catering proposal with structured process, quality checks, and system integration +--- + +# Catering Proposal + +## Purpose + +Create a comprehensive catering proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing catering proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the catering proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the catering proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Catering Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/cocktail-menu/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/cocktail-menu/SKILL.md new file mode 100644 index 0000000..19b74a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/cocktail-menu/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cocktail menu with structured process, quality checks, and system integration +--- + +# Cocktail Menu + +## Purpose + +Create a comprehensive cocktail menu that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cocktail menu documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cocktail menu +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cocktail menu using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Cocktail Menu + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/concept-development/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/concept-development/SKILL.md new file mode 100644 index 0000000..47a0a75 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/concept-development/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a concept development with structured process, quality checks, and system integration +--- + +# Concept Development + +## Purpose + +Create a comprehensive concept development that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing concept development documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the concept development +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the concept development using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Concept Development + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/cross-training-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/cross-training-plan/SKILL.md new file mode 100644 index 0000000..0c84a0f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/cross-training-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a cross training plan with structured process, quality checks, and system integration +--- + +# Cross Training Plan + +## Purpose + +Design and document a comprehensive cross training plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross training plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross training plan +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross training plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Cross Training Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/customer-feedback-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/customer-feedback-restaurant/SKILL.md new file mode 100644 index 0000000..dca294e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/customer-feedback-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a customer feedback restaurant with structured process, quality checks, and system integration +--- + +# Customer Feedback Restaurant + +## Purpose + +Create a comprehensive customer feedback restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer feedback restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer feedback restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer feedback restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Customer Feedback Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/delivery-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/delivery-optimization/SKILL.md new file mode 100644 index 0000000..267845c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/delivery-optimization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a delivery optimization with structured process, quality checks, and system integration +--- + +# Delivery Optimization + +## Purpose + +Create a comprehensive delivery optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing delivery optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the delivery optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the delivery optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Delivery Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/event-menu-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/event-menu-planning/SKILL.md new file mode 100644 index 0000000..23931a7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/event-menu-planning/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a event menu planning with structured process, quality checks, and system integration +--- + +# Event Menu Planning + +## Purpose + +Design and document a comprehensive event menu planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event menu planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event menu planning +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event menu planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Event Menu Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/food-cost-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/food-cost-analysis/SKILL.md new file mode 100644 index 0000000..4cf32dc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/food-cost-analysis/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a food cost analysis with structured process, quality checks, and system integration +--- + +# Food Cost Analysis + +## Purpose + +Analyze and produce a comprehensive food cost analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing food cost analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the food cost analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the food cost analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Food Cost Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/food-safety-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/food-safety-plan/SKILL.md new file mode 100644 index 0000000..91b320f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/food-safety-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a food safety plan with structured process, quality checks, and system integration +--- + +# Food Safety Plan + +## Purpose + +Design and document a comprehensive food safety plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing food safety plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the food safety plan +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the food safety plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Food Safety Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/franchise-operations-manual/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/franchise-operations-manual/SKILL.md new file mode 100644 index 0000000..67c8447 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/franchise-operations-manual/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a franchise operations manual with structured process, quality checks, and system integration +--- + +# Franchise Operations Manual + +## Purpose + +Create a comprehensive franchise operations manual that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing franchise operations manual documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the franchise operations manual +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the franchise operations manual using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Franchise Operations Manual + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/haccp-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/haccp-plan/SKILL.md new file mode 100644 index 0000000..79b1e4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/haccp-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a haccp plan with structured process, quality checks, and system integration +--- + +# Haccp Plan + +## Purpose + +Design and document a comprehensive haccp plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing haccp plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the haccp plan +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the haccp plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Haccp Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/health-inspection-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/health-inspection-prep/SKILL.md new file mode 100644 index 0000000..d51853e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/health-inspection-prep/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a health inspection prep with structured process, quality checks, and system integration +--- + +# Health Inspection Prep + +## Purpose + +Create a comprehensive health inspection prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing health inspection prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the health inspection prep +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the health inspection prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Health Inspection Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/influencer-dining/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/influencer-dining/SKILL.md new file mode 100644 index 0000000..c125422 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/influencer-dining/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a influencer dining with structured process, quality checks, and system integration +--- + +# Influencer Dining + +## Purpose + +Create a comprehensive influencer dining that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing influencer dining documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the influencer dining +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the influencer dining using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Influencer Dining + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/ingredient-sourcing/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/ingredient-sourcing/SKILL.md new file mode 100644 index 0000000..fe59d8d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/ingredient-sourcing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ingredient sourcing with structured process, quality checks, and system integration +--- + +# Ingredient Sourcing + +## Purpose + +Create a comprehensive ingredient sourcing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ingredient sourcing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ingredient sourcing +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ingredient sourcing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Ingredient Sourcing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/inventory-management-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/inventory-management-restaurant/SKILL.md new file mode 100644 index 0000000..a72ca3d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/inventory-management-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a inventory management restaurant with structured process, quality checks, and system integration +--- + +# Inventory Management Restaurant + +## Purpose + +Create a comprehensive inventory management restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inventory management restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inventory management restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inventory management restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Inventory Management Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/labor-scheduling/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/labor-scheduling/SKILL.md new file mode 100644 index 0000000..018055e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/labor-scheduling/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a labor scheduling with structured process, quality checks, and system integration +--- + +# Labor Scheduling + +## Purpose + +Create a comprehensive labor scheduling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing labor scheduling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the labor scheduling +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the labor scheduling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Labor Scheduling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/loyalty-program-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/loyalty-program-restaurant/SKILL.md new file mode 100644 index 0000000..a846f44 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/loyalty-program-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a loyalty program restaurant with structured process, quality checks, and system integration +--- + +# Loyalty Program Restaurant + +## Purpose + +Design and document a comprehensive loyalty program restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing loyalty program restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the loyalty program restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the loyalty program restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Loyalty Program Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/market-feasibility/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/market-feasibility/SKILL.md new file mode 100644 index 0000000..071ada5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/market-feasibility/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a market feasibility with structured process, quality checks, and system integration +--- + +# Market Feasibility + +## Purpose + +Create a comprehensive market feasibility that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market feasibility documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market feasibility +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market feasibility using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Market Feasibility + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/marketing-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/marketing-restaurant/SKILL.md new file mode 100644 index 0000000..aa21285 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/marketing-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a marketing restaurant with structured process, quality checks, and system integration +--- + +# Marketing Restaurant + +## Purpose + +Create a comprehensive marketing restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Marketing Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/menu-costing/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/menu-costing/SKILL.md new file mode 100644 index 0000000..b4e12f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/menu-costing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a menu costing with structured process, quality checks, and system integration +--- + +# Menu Costing + +## Purpose + +Create a comprehensive menu costing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing menu costing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the menu costing +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the menu costing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Menu Costing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/menu-design/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/menu-design/SKILL.md new file mode 100644 index 0000000..4a2bd0a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/menu-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a menu design with structured process, quality checks, and system integration +--- + +# Menu Design + +## Purpose + +Create a comprehensive menu design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing menu design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the menu design +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the menu design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Menu Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/menu-engineering/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/menu-engineering/SKILL.md new file mode 100644 index 0000000..bef290a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/menu-engineering/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a menu engineering with structured process, quality checks, and system integration +--- + +# Menu Engineering + +## Purpose + +Create a comprehensive menu engineering that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing menu engineering documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the menu engineering +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the menu engineering using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Menu Engineering + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/online-ordering-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/online-ordering-setup/SKILL.md new file mode 100644 index 0000000..0d6d59c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/online-ordering-setup/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a online ordering setup with structured process, quality checks, and system integration +--- + +# Online Ordering Setup + +## Purpose + +Design and document a comprehensive online ordering setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing online ordering setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the online ordering setup +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the online ordering setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Online Ordering Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/opening-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/opening-checklist/SKILL.md new file mode 100644 index 0000000..7bc231a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/opening-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a opening checklist with structured process, quality checks, and system integration +--- + +# Opening Checklist + +## Purpose + +Analyze and produce a comprehensive opening checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing opening checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the opening checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the opening checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Opening Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/par-level-setting/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/par-level-setting/SKILL.md new file mode 100644 index 0000000..9d6eee8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/par-level-setting/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a par level setting with structured process, quality checks, and system integration +--- + +# Par Level Setting + +## Purpose + +Create a comprehensive par level setting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing par level setting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the par level setting +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the par level setting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Par Level Setting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/peak-hour-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/peak-hour-planning/SKILL.md new file mode 100644 index 0000000..bf4d844 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/peak-hour-planning/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a peak hour planning with structured process, quality checks, and system integration +--- + +# Peak Hour Planning + +## Purpose + +Design and document a comprehensive peak hour planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing peak hour planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the peak hour planning +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the peak hour planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Peak Hour Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/portion-control/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/portion-control/SKILL.md new file mode 100644 index 0000000..ce49e12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/portion-control/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a portion control with structured process, quality checks, and system integration +--- + +# Portion Control + +## Purpose + +Create a comprehensive portion control that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing portion control documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the portion control +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the portion control using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Portion Control + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/recipe-scaling/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/recipe-scaling/SKILL.md new file mode 100644 index 0000000..828b18d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/recipe-scaling/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a recipe scaling with structured process, quality checks, and system integration +--- + +# Recipe Scaling + +## Purpose + +Create a comprehensive recipe scaling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recipe scaling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recipe scaling +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recipe scaling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Recipe Scaling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/recipe-standardization/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/recipe-standardization/SKILL.md new file mode 100644 index 0000000..8dbee82 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/recipe-standardization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a recipe standardization with structured process, quality checks, and system integration +--- + +# Recipe Standardization + +## Purpose + +Create a comprehensive recipe standardization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recipe standardization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recipe standardization +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recipe standardization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Recipe Standardization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/restaurant-business-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/restaurant-business-plan/SKILL.md new file mode 100644 index 0000000..35c23c6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/restaurant-business-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a restaurant business plan with structured process, quality checks, and system integration +--- + +# Restaurant Business Plan + +## Purpose + +Design and document a comprehensive restaurant business plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing restaurant business plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the restaurant business plan +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the restaurant business plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Restaurant Business Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/review-management-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/review-management-restaurant/SKILL.md new file mode 100644 index 0000000..fde45b5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/review-management-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a review management restaurant with structured process, quality checks, and system integration +--- + +# Review Management Restaurant + +## Purpose + +Analyze and produce a comprehensive review management restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review management restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review management restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review management restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Review Management Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/sanitation-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/sanitation-checklist/SKILL.md new file mode 100644 index 0000000..30387db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/sanitation-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a sanitation checklist with structured process, quality checks, and system integration +--- + +# Sanitation Checklist + +## Purpose + +Analyze and produce a comprehensive sanitation checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sanitation checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sanitation checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sanitation checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Sanitation Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/service-standards/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/service-standards/SKILL.md new file mode 100644 index 0000000..d0eb746 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/service-standards/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a service standards with structured process, quality checks, and system integration +--- + +# Service Standards + +## Purpose + +Create a comprehensive service standards that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing service standards documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the service standards +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the service standards using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Service Standards + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/social-media-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/social-media-restaurant/SKILL.md new file mode 100644 index 0000000..edfca98 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/social-media-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a social media restaurant with structured process, quality checks, and system integration +--- + +# Social Media Restaurant + +## Purpose + +Create a comprehensive social media restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Social Media Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/staff-training-restaurant/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/staff-training-restaurant/SKILL.md new file mode 100644 index 0000000..baa9820 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/staff-training-restaurant/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a staff training restaurant with structured process, quality checks, and system integration +--- + +# Staff Training Restaurant + +## Purpose + +Create a comprehensive staff training restaurant that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing staff training restaurant documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the staff training restaurant +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the staff training restaurant using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Staff Training Restaurant + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/temperature-log/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/temperature-log/SKILL.md new file mode 100644 index 0000000..014c655 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/temperature-log/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a temperature log with structured process, quality checks, and system integration +--- + +# Temperature Log + +## Purpose + +Create a comprehensive temperature log that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing temperature log documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the temperature log +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the temperature log using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Temperature Log + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/vendor-negotiation/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/vendor-negotiation/SKILL.md new file mode 100644 index 0000000..fe930f7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/vendor-negotiation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a vendor negotiation with structured process, quality checks, and system integration +--- + +# Vendor Negotiation + +## Purpose + +Create a comprehensive vendor negotiation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor negotiation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor negotiation +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor negotiation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Vendor Negotiation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/waste-reduction/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/waste-reduction/SKILL.md new file mode 100644 index 0000000..9f84bd8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/waste-reduction/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a waste reduction with structured process, quality checks, and system integration +--- + +# Waste Reduction + +## Purpose + +Create a comprehensive waste reduction that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing waste reduction documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the waste reduction +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the waste reduction using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Waste Reduction + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/food-beverage/wine-pairing/SKILL.md b/clowdex-download/.claude/.claude/skills/food-beverage/wine-pairing/SKILL.md new file mode 100644 index 0000000..975391c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/food-beverage/wine-pairing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a wine pairing with structured process, quality checks, and system integration +--- + +# Wine Pairing + +## Purpose + +Create a comprehensive wine pairing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Food & Beverage + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wine pairing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Menu Engineering Matrix, HACCP (Hazard Analysis Critical Control Points), Prime Cost Management + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wine pairing +- Identify gaps, opportunities, and risks +- Define success metrics: Food Cost % (target: 28-32%), Labor Cost % (target: 25-30%), Prime Cost % (target: 55-65%), Table Turnover Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wine pairing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Menu engineering quarterly (stars, plowhorses, puzzles, dogs) + +## Output Format + +```markdown +# Wine Pairing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Menu Engineering Matrix +- HACCP (Hazard Analysis Critical Control Points) +- Prime Cost Management +- Service Blueprint +- Brand Architecture + +## Key Metrics +- Food Cost % (target: 28-32%) +- Labor Cost % (target: 25-30%) +- Prime Cost % (target: 55-65%) +- Table Turnover Rate +- Revenue Per Available Seat Hour +- Customer Satisfaction Score + +## Best Practices +- Menu engineering quarterly (stars, plowhorses, puzzles, dogs) +- Daily inventory counts on high-cost items +- Recipe costing for every menu item +- Cross-train all front-of-house staff +- Respond to negative reviews within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/appointment-reminder/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/appointment-reminder/SKILL.md new file mode 100644 index 0000000..3236c92 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/appointment-reminder/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a appointment reminder with structured process, quality checks, and system integration +--- + +# Appointment Reminder + +## Purpose + +Create a comprehensive appointment reminder that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing appointment reminder documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the appointment reminder +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the appointment reminder using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Appointment Reminder + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/billing-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/billing-audit/SKILL.md new file mode 100644 index 0000000..0cfa1d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/billing-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a billing audit with structured process, quality checks, and system integration +--- + +# Billing Audit + +## Purpose + +Analyze and produce a comprehensive billing audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing billing audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the billing audit +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the billing audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Billing Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/breach-response/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/breach-response/SKILL.md new file mode 100644 index 0000000..f0f2a67 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/breach-response/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a breach response with structured process, quality checks, and system integration +--- + +# Breach Response + +## Purpose + +Create a comprehensive breach response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breach response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breach response +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breach response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Breach Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/care-coordination/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/care-coordination/SKILL.md new file mode 100644 index 0000000..6977ddb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/care-coordination/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a care coordination with structured process, quality checks, and system integration +--- + +# Care Coordination + +## Purpose + +Create a comprehensive care coordination that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing care coordination documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the care coordination +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the care coordination using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Care Coordination + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/care-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/care-plan/SKILL.md new file mode 100644 index 0000000..d8785c9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/care-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a care plan with structured process, quality checks, and system integration +--- + +# Care Plan + +## Purpose + +Design and document a comprehensive care plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing care plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the care plan +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the care plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Care Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/chronic-disease-management/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/chronic-disease-management/SKILL.md new file mode 100644 index 0000000..f581012 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/chronic-disease-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a chronic disease management with structured process, quality checks, and system integration +--- + +# Chronic Disease Management + +## Purpose + +Create a comprehensive chronic disease management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chronic disease management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chronic disease management +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chronic disease management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Chronic Disease Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/clinical-trial-recruitment/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/clinical-trial-recruitment/SKILL.md new file mode 100644 index 0000000..bdeee99 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/clinical-trial-recruitment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a clinical trial recruitment with structured process, quality checks, and system integration +--- + +# Clinical Trial Recruitment + +## Purpose + +Create a comprehensive clinical trial recruitment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing clinical trial recruitment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the clinical trial recruitment +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the clinical trial recruitment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Clinical Trial Recruitment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/coding-accuracy/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/coding-accuracy/SKILL.md new file mode 100644 index 0000000..37218ae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/coding-accuracy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a coding accuracy with structured process, quality checks, and system integration +--- + +# Coding Accuracy + +## Purpose + +Create a comprehensive coding accuracy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing coding accuracy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the coding accuracy +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the coding accuracy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Coding Accuracy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/condition-explainer/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/condition-explainer/SKILL.md new file mode 100644 index 0000000..ea5e317 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/condition-explainer/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a condition explainer with structured process, quality checks, and system integration +--- + +# Condition Explainer + +## Purpose + +Create a comprehensive condition explainer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing condition explainer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the condition explainer +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the condition explainer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Condition Explainer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/consent-form/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/consent-form/SKILL.md new file mode 100644 index 0000000..af6beba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/consent-form/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a consent form with structured process, quality checks, and system integration +--- + +# Consent Form + +## Purpose + +Create a comprehensive consent form that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing consent form documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the consent form +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the consent form using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Consent Form + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/corporate-wellness/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/corporate-wellness/SKILL.md new file mode 100644 index 0000000..5ad07da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/corporate-wellness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a corporate wellness with structured process, quality checks, and system integration +--- + +# Corporate Wellness + +## Purpose + +Create a comprehensive corporate wellness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate wellness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate wellness +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate wellness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Corporate Wellness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/credentialing-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/credentialing-checklist/SKILL.md new file mode 100644 index 0000000..197939e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/credentialing-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a credentialing checklist with structured process, quality checks, and system integration +--- + +# Credentialing Checklist + +## Purpose + +Analyze and produce a comprehensive credentialing checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing credentialing checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the credentialing checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the credentialing checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Credentialing Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/discharge-instructions/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/discharge-instructions/SKILL.md new file mode 100644 index 0000000..4da8f5c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/discharge-instructions/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a discharge instructions with structured process, quality checks, and system integration +--- + +# Discharge Instructions + +## Purpose + +Create a comprehensive discharge instructions that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing discharge instructions documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the discharge instructions +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the discharge instructions using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Discharge Instructions + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/follow-up-message/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/follow-up-message/SKILL.md new file mode 100644 index 0000000..f541feb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/follow-up-message/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a follow up message with structured process, quality checks, and system integration +--- + +# Follow Up Message + +## Purpose + +Create a comprehensive follow up message that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing follow up message documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the follow up message +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the follow up message using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Follow Up Message + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/health-content-article/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/health-content-article/SKILL.md new file mode 100644 index 0000000..67debd7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/health-content-article/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a health content article with structured process, quality checks, and system integration +--- + +# Health Content Article + +## Purpose + +Create a comprehensive health content article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing health content article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the health content article +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the health content article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Health Content Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/hipaa-compliance-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/hipaa-compliance-checklist/SKILL.md new file mode 100644 index 0000000..584259b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/hipaa-compliance-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a hipaa compliance checklist with structured process, quality checks, and system integration +--- + +# Hipaa Compliance Checklist + +## Purpose + +Analyze and produce a comprehensive hipaa compliance checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hipaa compliance checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hipaa compliance checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hipaa compliance checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Hipaa Compliance Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/infection-control/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/infection-control/SKILL.md new file mode 100644 index 0000000..ff2a593 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/infection-control/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a infection control with structured process, quality checks, and system integration +--- + +# Infection Control + +## Purpose + +Create a comprehensive infection control that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing infection control documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the infection control +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the infection control using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Infection Control + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/informed-consent/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/informed-consent/SKILL.md new file mode 100644 index 0000000..32ce03e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/informed-consent/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a informed consent with structured process, quality checks, and system integration +--- + +# Informed Consent + +## Purpose + +Create a comprehensive informed consent that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing informed consent documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the informed consent +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the informed consent using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Informed Consent + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/insurance-verification/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/insurance-verification/SKILL.md new file mode 100644 index 0000000..141bd7d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/insurance-verification/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a insurance verification with structured process, quality checks, and system integration +--- + +# Insurance Verification + +## Purpose + +Create a comprehensive insurance verification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing insurance verification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the insurance verification +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the insurance verification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Insurance Verification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/medical-history-form/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/medical-history-form/SKILL.md new file mode 100644 index 0000000..ac41647 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/medical-history-form/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a medical history form with structured process, quality checks, and system integration +--- + +# Medical History Form + +## Purpose + +Create a comprehensive medical history form that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing medical history form documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the medical history form +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the medical history form using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Medical History Form + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/mental-health-resources-health/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/mental-health-resources-health/SKILL.md new file mode 100644 index 0000000..1876039 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/mental-health-resources-health/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mental health resources health with structured process, quality checks, and system integration +--- + +# Mental Health Resources Health + +## Purpose + +Create a comprehensive mental health resources health that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mental health resources health documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mental health resources health +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mental health resources health using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Mental Health Resources Health + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/online-reputation-management/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/online-reputation-management/SKILL.md new file mode 100644 index 0000000..abeb6e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/online-reputation-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a online reputation management with structured process, quality checks, and system integration +--- + +# Online Reputation Management + +## Purpose + +Create a comprehensive online reputation management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing online reputation management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the online reputation management +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the online reputation management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Online Reputation Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-acquisition/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-acquisition/SKILL.md new file mode 100644 index 0000000..256cfd4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-acquisition/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a patient acquisition with structured process, quality checks, and system integration +--- + +# Patient Acquisition + +## Purpose + +Create a comprehensive patient acquisition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient acquisition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient acquisition +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient acquisition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Acquisition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-communication/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-communication/SKILL.md new file mode 100644 index 0000000..c66964e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-communication/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a patient communication with structured process, quality checks, and system integration +--- + +# Patient Communication + +## Purpose + +Create a comprehensive patient communication that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient communication documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient communication +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient communication using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Communication + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-education-material/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-education-material/SKILL.md new file mode 100644 index 0000000..ba94c51 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-education-material/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a patient education material with structured process, quality checks, and system integration +--- + +# Patient Education Material + +## Purpose + +Create a comprehensive patient education material that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient education material documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient education material +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient education material using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Education Material + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-intake-form/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-intake-form/SKILL.md new file mode 100644 index 0000000..feea1e1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-intake-form/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a patient intake form with structured process, quality checks, and system integration +--- + +# Patient Intake Form + +## Purpose + +Create a comprehensive patient intake form that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient intake form documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient intake form +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient intake form using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Intake Form + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-portal-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-portal-guide/SKILL.md new file mode 100644 index 0000000..0d0ed7d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-portal-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a patient portal guide with structured process, quality checks, and system integration +--- + +# Patient Portal Guide + +## Purpose + +Design and document a comprehensive patient portal guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient portal guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient portal guide +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient portal guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Portal Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/patient-satisfaction-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/patient-satisfaction-survey/SKILL.md new file mode 100644 index 0000000..e5d9fd4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/patient-satisfaction-survey/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a patient satisfaction survey with structured process, quality checks, and system integration +--- + +# Patient Satisfaction Survey + +## Purpose + +Create a comprehensive patient satisfaction survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patient satisfaction survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patient satisfaction survey +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patient satisfaction survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Patient Satisfaction Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/population-health-report/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/population-health-report/SKILL.md new file mode 100644 index 0000000..249b1b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/population-health-report/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a population health report with structured process, quality checks, and system integration +--- + +# Population Health Report + +## Purpose + +Analyze and produce a comprehensive population health report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing population health report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the population health report +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the population health report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Population Health Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/practice-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/practice-dashboard/SKILL.md new file mode 100644 index 0000000..a0b3410 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/practice-dashboard/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a practice dashboard with structured process, quality checks, and system integration +--- + +# Practice Dashboard + +## Purpose + +Analyze and produce a comprehensive practice dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing practice dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the practice dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the practice dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Practice Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/practice-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/practice-marketing-plan/SKILL.md new file mode 100644 index 0000000..f3f200c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/practice-marketing-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a practice marketing plan with structured process, quality checks, and system integration +--- + +# Practice Marketing Plan + +## Purpose + +Design and document a comprehensive practice marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing practice marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the practice marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the practice marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Practice Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/preventive-care-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/preventive-care-plan/SKILL.md new file mode 100644 index 0000000..fab3ecc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/preventive-care-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a preventive care plan with structured process, quality checks, and system integration +--- + +# Preventive Care Plan + +## Purpose + +Design and document a comprehensive preventive care plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing preventive care plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the preventive care plan +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the preventive care plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Preventive Care Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/privacy-notice/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/privacy-notice/SKILL.md new file mode 100644 index 0000000..65defea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/privacy-notice/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a privacy notice with structured process, quality checks, and system integration +--- + +# Privacy Notice + +## Purpose + +Create a comprehensive privacy notice that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing privacy notice documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the privacy notice +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the privacy notice using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Privacy Notice + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/provider-enrollment/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/provider-enrollment/SKILL.md new file mode 100644 index 0000000..02235ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/provider-enrollment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a provider enrollment with structured process, quality checks, and system integration +--- + +# Provider Enrollment + +## Purpose + +Create a comprehensive provider enrollment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing provider enrollment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the provider enrollment +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the provider enrollment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Provider Enrollment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/quality-metrics/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/quality-metrics/SKILL.md new file mode 100644 index 0000000..0f3d7ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/quality-metrics/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a quality metrics with structured process, quality checks, and system integration +--- + +# Quality Metrics + +## Purpose + +Analyze and produce a comprehensive quality metrics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quality metrics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quality metrics +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quality metrics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Quality Metrics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/referral-management/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/referral-management/SKILL.md new file mode 100644 index 0000000..0773478 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/referral-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a referral management with structured process, quality checks, and system integration +--- + +# Referral Management + +## Purpose + +Create a comprehensive referral management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral management +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Referral Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/referral-program-health/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/referral-program-health/SKILL.md new file mode 100644 index 0000000..7edb8c5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/referral-program-health/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a referral program health with structured process, quality checks, and system integration +--- + +# Referral Program Health + +## Purpose + +Design and document a comprehensive referral program health that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral program health documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral program health +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral program health using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Referral Program Health + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/research-protocol-summary/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/research-protocol-summary/SKILL.md new file mode 100644 index 0000000..017af0d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/research-protocol-summary/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a research protocol summary with structured process, quality checks, and system integration +--- + +# Research Protocol Summary + +## Purpose + +Create a comprehensive research protocol summary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing research protocol summary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the research protocol summary +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the research protocol summary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Research Protocol Summary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/revenue-cycle-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/revenue-cycle-optimization/SKILL.md new file mode 100644 index 0000000..b0f7ff1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/revenue-cycle-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a revenue cycle optimization with structured process, quality checks, and system integration +--- + +# Revenue Cycle Optimization + +## Purpose + +Create a comprehensive revenue cycle optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing revenue cycle optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the revenue cycle optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the revenue cycle optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Revenue Cycle Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/review-response-healthcare/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/review-response-healthcare/SKILL.md new file mode 100644 index 0000000..7a69dc1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/review-response-healthcare/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a review response healthcare with structured process, quality checks, and system integration +--- + +# Review Response Healthcare + +## Purpose + +Analyze and produce a comprehensive review response healthcare that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review response healthcare documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review response healthcare +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review response healthcare using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Review Response Healthcare + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/safety-protocol/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/safety-protocol/SKILL.md new file mode 100644 index 0000000..3c14e26 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/safety-protocol/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a safety protocol with structured process, quality checks, and system integration +--- + +# Safety Protocol + +## Purpose + +Create a comprehensive safety protocol that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing safety protocol documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the safety protocol +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the safety protocol using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Safety Protocol + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/staff-training-healthcare/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/staff-training-healthcare/SKILL.md new file mode 100644 index 0000000..b4ada74 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/staff-training-healthcare/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a staff training healthcare with structured process, quality checks, and system integration +--- + +# Staff Training Healthcare + +## Purpose + +Create a comprehensive staff training healthcare that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing staff training healthcare documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the staff training healthcare +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the staff training healthcare using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Staff Training Healthcare + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/telehealth-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/telehealth-setup/SKILL.md new file mode 100644 index 0000000..344c2fa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/telehealth-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a telehealth setup with structured process, quality checks, and system integration +--- + +# Telehealth Setup + +## Purpose + +Design and document a comprehensive telehealth setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing telehealth setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the telehealth setup +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the telehealth setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Telehealth Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/testimonial-request-health/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/testimonial-request-health/SKILL.md new file mode 100644 index 0000000..1b28837 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/testimonial-request-health/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a testimonial request health with structured process, quality checks, and system integration +--- + +# Testimonial Request Health + +## Purpose + +Create a comprehensive testimonial request health that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing testimonial request health documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the testimonial request health +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the testimonial request health using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Testimonial Request Health + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/transition-of-care/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/transition-of-care/SKILL.md new file mode 100644 index 0000000..d5b6087 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/transition-of-care/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a transition of care with structured process, quality checks, and system integration +--- + +# Transition Of Care + +## Purpose + +Create a comprehensive transition of care that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing transition of care documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the transition of care +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the transition of care using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Transition Of Care + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/treatment-plan-template/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/treatment-plan-template/SKILL.md new file mode 100644 index 0000000..8fb38dc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/treatment-plan-template/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a treatment plan template with structured process, quality checks, and system integration +--- + +# Treatment Plan Template + +## Purpose + +Create a comprehensive treatment plan template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing treatment plan template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the treatment plan template +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the treatment plan template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Treatment Plan Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/virtual-visit-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/virtual-visit-guide/SKILL.md new file mode 100644 index 0000000..82259e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/virtual-visit-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a virtual visit guide with structured process, quality checks, and system integration +--- + +# Virtual Visit Guide + +## Purpose + +Design and document a comprehensive virtual visit guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing virtual visit guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the virtual visit guide +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the virtual visit guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Virtual Visit Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/healthcare/wellness-program/SKILL.md b/clowdex-download/.claude/.claude/skills/healthcare/wellness-program/SKILL.md new file mode 100644 index 0000000..f0190db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/healthcare/wellness-program/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a wellness program with structured process, quality checks, and system integration +--- + +# Wellness Program + +## Purpose + +Design and document a comprehensive wellness program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Healthcare + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wellness program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: HIPAA Compliance Framework, Patient-Centered Medical Home, Plan-Do-Study-Act (PDSA) Cycle + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wellness program +- Identify gaps, opportunities, and risks +- Define success metrics: Patient Satisfaction Score, Wait Time, No-Show Rate, Patient Retention +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wellness program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: HIPAA compliance in every patient communication + +## Output Format + +```markdown +# Wellness Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- HIPAA Compliance Framework +- Patient-Centered Medical Home +- Plan-Do-Study-Act (PDSA) Cycle +- HCAHPS Framework +- Value-Based Care Model + +## Key Metrics +- Patient Satisfaction Score +- Wait Time +- No-Show Rate +- Patient Retention +- Revenue Per Visit +- Claim Denial Rate +- Readmission Rate + +## Best Practices +- HIPAA compliance in every patient communication +- Appointment reminders 48 hours and 2 hours before +- Document within 24 hours of encounter +- Follow up on abnormal results within 48 hours +- DISCLAIMER: Skills provide operational templates — not medical advice + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/30-60-90-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/30-60-90-plan/SKILL.md new file mode 100644 index 0000000..b0bde92 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/30-60-90-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a 30 60 90 plan with structured process, quality checks, and system integration +--- + +# 30 60 90 Plan + +## Purpose + +Design and document a comprehensive 30 60 90 plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing 30 60 90 plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the 30 60 90 plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the 30 60 90 plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# 30 60 90 Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/all-hands-agenda/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/all-hands-agenda/SKILL.md new file mode 100644 index 0000000..386c9ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/all-hands-agenda/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a all hands agenda with structured process, quality checks, and system integration +--- + +# All Hands Agenda + +## Purpose + +Create a comprehensive all hands agenda that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing all hands agenda documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the all hands agenda +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the all hands agenda using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# All Hands Agenda + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/attrition-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/attrition-analysis/SKILL.md new file mode 100644 index 0000000..468ee11 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/attrition-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a attrition analysis with structured process, quality checks, and system integration +--- + +# Attrition Analysis + +## Purpose + +Analyze and produce a comprehensive attrition analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing attrition analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the attrition analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the attrition analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Attrition Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/benefits-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/benefits-comparison/SKILL.md new file mode 100644 index 0000000..0742b63 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/benefits-comparison/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a benefits comparison with structured process, quality checks, and system integration +--- + +# Benefits Comparison + +## Purpose + +Analyze and produce a comprehensive benefits comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing benefits comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the benefits comparison +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the benefits comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Benefits Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/buddy-system-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/buddy-system-guide/SKILL.md new file mode 100644 index 0000000..769f32b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/buddy-system-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a buddy system guide with structured process, quality checks, and system integration +--- + +# Buddy System Guide + +## Purpose + +Design and document a comprehensive buddy system guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing buddy system guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the buddy system guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the buddy system guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Buddy System Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/candidate-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/candidate-evaluation/SKILL.md new file mode 100644 index 0000000..afe1100 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/candidate-evaluation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a candidate evaluation with structured process, quality checks, and system integration +--- + +# Candidate Evaluation + +## Purpose + +Analyze and produce a comprehensive candidate evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing candidate evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the candidate evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the candidate evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Candidate Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/career-development-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/career-development-plan/SKILL.md new file mode 100644 index 0000000..f4ed00b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/career-development-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a career development plan with structured process, quality checks, and system integration +--- + +# Career Development Plan + +## Purpose + +Design and document a comprehensive career development plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing career development plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the career development plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the career development plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Career Development Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/coaching-conversation/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/coaching-conversation/SKILL.md new file mode 100644 index 0000000..fcb873f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/coaching-conversation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a coaching conversation with structured process, quality checks, and system integration +--- + +# Coaching Conversation + +## Purpose + +Create a comprehensive coaching conversation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing coaching conversation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the coaching conversation +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the coaching conversation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Coaching Conversation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/compensation-review/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/compensation-review/SKILL.md new file mode 100644 index 0000000..2b1af83 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/compensation-review/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a compensation review with structured process, quality checks, and system integration +--- + +# Compensation Review + +## Purpose + +Analyze and produce a comprehensive compensation review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compensation review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compensation review +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compensation review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Compensation Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/conflict-resolution/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/conflict-resolution/SKILL.md new file mode 100644 index 0000000..8571ee9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/conflict-resolution/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a conflict resolution with structured process, quality checks, and system integration +--- + +# Conflict Resolution + +## Purpose + +Create a comprehensive conflict resolution that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conflict resolution documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conflict resolution +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conflict resolution using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Conflict Resolution + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/contractor-management/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/contractor-management/SKILL.md new file mode 100644 index 0000000..b29364f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/contractor-management/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a contractor management with structured process, quality checks, and system integration +--- + +# Contractor Management + +## Purpose + +Create a comprehensive contractor management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing contractor management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the contractor management +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the contractor management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Contractor Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/culture-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/culture-deck/SKILL.md new file mode 100644 index 0000000..c96c723 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/culture-deck/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a culture deck with structured process, quality checks, and system integration +--- + +# Culture Deck + +## Purpose + +Create a comprehensive culture deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing culture deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the culture deck +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the culture deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Culture Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/culture-values-definition/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/culture-values-definition/SKILL.md new file mode 100644 index 0000000..1e3aca7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/culture-values-definition/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a culture values definition with structured process, quality checks, and system integration +--- + +# Culture Values Definition + +## Purpose + +Create a comprehensive culture values definition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing culture values definition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the culture values definition +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the culture values definition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Culture Values Definition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/dei-metrics/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/dei-metrics/SKILL.md new file mode 100644 index 0000000..70a1f2a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/dei-metrics/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a dei metrics with structured process, quality checks, and system integration +--- + +# Dei Metrics + +## Purpose + +Analyze and produce a comprehensive dei metrics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dei metrics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dei metrics +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dei metrics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Dei Metrics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/dei-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/dei-strategy/SKILL.md new file mode 100644 index 0000000..713a78c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/dei-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a dei strategy with structured process, quality checks, and system integration +--- + +# Dei Strategy + +## Purpose + +Design and document a comprehensive dei strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dei strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dei strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dei strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Dei Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/employee-engagement-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/employee-engagement-survey/SKILL.md new file mode 100644 index 0000000..71be5e9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/employee-engagement-survey/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a employee engagement survey with structured process, quality checks, and system integration +--- + +# Employee Engagement Survey + +## Purpose + +Create a comprehensive employee engagement survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employee engagement survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employee engagement survey +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employee engagement survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Employee Engagement Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/employee-handbook/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/employee-handbook/SKILL.md new file mode 100644 index 0000000..93d62f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/employee-handbook/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a employee handbook with structured process, quality checks, and system integration +--- + +# Employee Handbook + +## Purpose + +Create a comprehensive employee handbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employee handbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employee handbook +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employee handbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Employee Handbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/employer-brand/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/employer-brand/SKILL.md new file mode 100644 index 0000000..2d1c2fd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/employer-brand/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a employer brand with structured process, quality checks, and system integration +--- + +# Employer Brand + +## Purpose + +Create a comprehensive employer brand that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employer brand documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employer brand +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employer brand using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Employer Brand + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/exit-interview/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/exit-interview/SKILL.md new file mode 100644 index 0000000..95f6e71 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/exit-interview/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a exit interview with structured process, quality checks, and system integration +--- + +# Exit Interview + +## Purpose + +Create a comprehensive exit interview that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing exit interview documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the exit interview +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the exit interview using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Exit Interview + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/feedback-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/feedback-framework/SKILL.md new file mode 100644 index 0000000..474db89 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/feedback-framework/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a feedback framework with structured process, quality checks, and system integration +--- + +# Feedback Framework + +## Purpose + +Design and document a comprehensive feedback framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feedback framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feedback framework +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feedback framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Feedback Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/grievance-procedure/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/grievance-procedure/SKILL.md new file mode 100644 index 0000000..6942be9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/grievance-procedure/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a grievance procedure with structured process, quality checks, and system integration +--- + +# Grievance Procedure + +## Purpose + +Create a comprehensive grievance procedure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grievance procedure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grievance procedure +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grievance procedure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Grievance Procedure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/hiring-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/hiring-plan/SKILL.md new file mode 100644 index 0000000..f00ce7d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/hiring-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a hiring plan with structured process, quality checks, and system integration +--- + +# Hiring Plan + +## Purpose + +Design and document a comprehensive hiring plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hiring plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hiring plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hiring plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Hiring Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/hr-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/hr-dashboard/SKILL.md new file mode 100644 index 0000000..0ae0189 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/hr-dashboard/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a hr dashboard with structured process, quality checks, and system integration +--- + +# Hr Dashboard + +## Purpose + +Analyze and produce a comprehensive hr dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hr dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hr dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hr dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Hr Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/hybrid-work-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/hybrid-work-policy/SKILL.md new file mode 100644 index 0000000..5062f1e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/hybrid-work-policy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a hybrid work policy with structured process, quality checks, and system integration +--- + +# Hybrid Work Policy + +## Purpose + +Create a comprehensive hybrid work policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hybrid work policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hybrid work policy +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hybrid work policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Hybrid Work Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/inclusive-hiring-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/inclusive-hiring-guide/SKILL.md new file mode 100644 index 0000000..945d5d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/inclusive-hiring-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a inclusive hiring guide with structured process, quality checks, and system integration +--- + +# Inclusive Hiring Guide + +## Purpose + +Design and document a comprehensive inclusive hiring guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inclusive hiring guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inclusive hiring guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inclusive hiring guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Inclusive Hiring Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/individual-development-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/individual-development-plan/SKILL.md new file mode 100644 index 0000000..621ac20 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/individual-development-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a individual development plan with structured process, quality checks, and system integration +--- + +# Individual Development Plan + +## Purpose + +Design and document a comprehensive individual development plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing individual development plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the individual development plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the individual development plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Individual Development Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/interview-question-bank/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/interview-question-bank/SKILL.md new file mode 100644 index 0000000..c50b485 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/interview-question-bank/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a interview question bank with structured process, quality checks, and system integration +--- + +# Interview Question Bank + +## Purpose + +Create a comprehensive interview question bank that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interview question bank documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interview question bank +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interview question bank using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Interview Question Bank + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/interview-scorecard/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/interview-scorecard/SKILL.md new file mode 100644 index 0000000..c602a62 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/interview-scorecard/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a interview scorecard with structured process, quality checks, and system integration +--- + +# Interview Scorecard + +## Purpose + +Analyze and produce a comprehensive interview scorecard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interview scorecard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interview scorecard +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interview scorecard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Interview Scorecard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/job-description/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/job-description/SKILL.md new file mode 100644 index 0000000..0500ef4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/job-description/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a job description with structured process, quality checks, and system integration +--- + +# Job Description + +## Purpose + +Create a comprehensive job description that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing job description documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the job description +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the job description using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Job Description + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/job-posting-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/job-posting-optimization/SKILL.md new file mode 100644 index 0000000..7c12544 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/job-posting-optimization/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a job posting optimization with structured process, quality checks, and system integration +--- + +# Job Posting Optimization + +## Purpose + +Create a comprehensive job posting optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing job posting optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the job posting optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the job posting optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Job Posting Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/mediation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/mediation-guide/SKILL.md new file mode 100644 index 0000000..67fa870 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/mediation-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a mediation guide with structured process, quality checks, and system integration +--- + +# Mediation Guide + +## Purpose + +Design and document a comprehensive mediation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mediation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mediation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mediation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Mediation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/mental-health-resources/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/mental-health-resources/SKILL.md new file mode 100644 index 0000000..b715ac0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/mental-health-resources/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a mental health resources with structured process, quality checks, and system integration +--- + +# Mental Health Resources + +## Purpose + +Create a comprehensive mental health resources that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mental health resources documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mental health resources +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mental health resources using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Mental Health Resources + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/offer-negotiation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/offer-negotiation-guide/SKILL.md new file mode 100644 index 0000000..1c43da8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/offer-negotiation-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a offer negotiation guide with structured process, quality checks, and system integration +--- + +# Offer Negotiation Guide + +## Purpose + +Design and document a comprehensive offer negotiation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing offer negotiation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the offer negotiation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the offer negotiation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Offer Negotiation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/offsite-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/offsite-planning/SKILL.md new file mode 100644 index 0000000..60bcac7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/offsite-planning/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a offsite planning with structured process, quality checks, and system integration +--- + +# Offsite Planning + +## Purpose + +Design and document a comprehensive offsite planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing offsite planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the offsite planning +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the offsite planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Offsite Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/onboarding-program/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/onboarding-program/SKILL.md new file mode 100644 index 0000000..b3a0fd8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/onboarding-program/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a onboarding program with structured process, quality checks, and system integration +--- + +# Onboarding Program + +## Purpose + +Design and document a comprehensive onboarding program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding program +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Onboarding Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/organizational-design/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/organizational-design/SKILL.md new file mode 100644 index 0000000..235c4af --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/organizational-design/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a organizational design with structured process, quality checks, and system integration +--- + +# Organizational Design + +## Purpose + +Create a comprehensive organizational design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing organizational design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the organizational design +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the organizational design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Organizational Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/peer-review-template/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/peer-review-template/SKILL.md new file mode 100644 index 0000000..be6923d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/peer-review-template/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a peer review template with structured process, quality checks, and system integration +--- + +# Peer Review Template + +## Purpose + +Analyze and produce a comprehensive peer review template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing peer review template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the peer review template +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the peer review template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Peer Review Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/people-analytics/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/people-analytics/SKILL.md new file mode 100644 index 0000000..d52a210 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/people-analytics/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a people analytics with structured process, quality checks, and system integration +--- + +# People Analytics + +## Purpose + +Create a comprehensive people analytics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing people analytics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the people analytics +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the people analytics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# People Analytics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/performance-review/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/performance-review/SKILL.md new file mode 100644 index 0000000..eacc59f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/performance-review/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a performance review with structured process, quality checks, and system integration +--- + +# Performance Review + +## Purpose + +Analyze and produce a comprehensive performance review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing performance review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the performance review +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the performance review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Performance Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/pip-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/pip-plan/SKILL.md new file mode 100644 index 0000000..a640864 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/pip-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a pip plan with structured process, quality checks, and system integration +--- + +# Pip Plan + +## Purpose + +Design and document a comprehensive pip plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pip plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pip plan +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pip plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Pip Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/pulse-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/pulse-survey/SKILL.md new file mode 100644 index 0000000..d4197ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/pulse-survey/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a pulse survey with structured process, quality checks, and system integration +--- + +# Pulse Survey + +## Purpose + +Create a comprehensive pulse survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pulse survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pulse survey +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pulse survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Pulse Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/recognition-program/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/recognition-program/SKILL.md new file mode 100644 index 0000000..49bf21f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/recognition-program/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a recognition program with structured process, quality checks, and system integration +--- + +# Recognition Program + +## Purpose + +Design and document a comprehensive recognition program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing recognition program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the recognition program +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the recognition program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Recognition Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/reference-check-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/reference-check-guide/SKILL.md new file mode 100644 index 0000000..90d6ae1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/reference-check-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a reference check guide with structured process, quality checks, and system integration +--- + +# Reference Check Guide + +## Purpose + +Analyze and produce a comprehensive reference check guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reference check guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reference check guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reference check guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Reference Check Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/remote-work-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/remote-work-policy/SKILL.md new file mode 100644 index 0000000..2e0f301 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/remote-work-policy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a remote work policy with structured process, quality checks, and system integration +--- + +# Remote Work Policy + +## Purpose + +Create a comprehensive remote work policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing remote work policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the remote work policy +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the remote work policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Remote Work Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/role-definition/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/role-definition/SKILL.md new file mode 100644 index 0000000..696f2f1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/role-definition/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a role definition with structured process, quality checks, and system integration +--- + +# Role Definition + +## Purpose + +Create a comprehensive role definition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing role definition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the role definition +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the role definition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Role Definition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/salary-negotiation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/salary-negotiation-guide/SKILL.md new file mode 100644 index 0000000..43b7fe8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/salary-negotiation-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a salary negotiation guide with structured process, quality checks, and system integration +--- + +# Salary Negotiation Guide + +## Purpose + +Design and document a comprehensive salary negotiation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing salary negotiation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the salary negotiation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the salary negotiation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Salary Negotiation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/self-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/self-assessment/SKILL.md new file mode 100644 index 0000000..e7087d4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/self-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a self assessment with structured process, quality checks, and system integration +--- + +# Self Assessment + +## Purpose + +Analyze and produce a comprehensive self assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing self assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the self assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the self assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Self Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/structured-interview-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/structured-interview-guide/SKILL.md new file mode 100644 index 0000000..7abd405 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/structured-interview-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a structured interview guide with structured process, quality checks, and system integration +--- + +# Structured Interview Guide + +## Purpose + +Design and document a comprehensive structured interview guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing structured interview guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the structured interview guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the structured interview guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Structured Interview Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/succession-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/succession-planning/SKILL.md new file mode 100644 index 0000000..827489e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/succession-planning/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a succession planning with structured process, quality checks, and system integration +--- + +# Succession Planning + +## Purpose + +Design and document a comprehensive succession planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing succession planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the succession planning +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the succession planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Succession Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/team-building-activity/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/team-building-activity/SKILL.md new file mode 100644 index 0000000..acd7206 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/team-building-activity/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a team building activity with structured process, quality checks, and system integration +--- + +# Team Building Activity + +## Purpose + +Create a comprehensive team building activity that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing team building activity documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the team building activity +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the team building activity using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Team Building Activity + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/team-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/team-structure/SKILL.md new file mode 100644 index 0000000..e22e8a0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/team-structure/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a team structure with structured process, quality checks, and system integration +--- + +# Team Structure + +## Purpose + +Create a comprehensive team structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing team structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the team structure +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the team structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Team Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/temp-to-perm-process/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/temp-to-perm-process/SKILL.md new file mode 100644 index 0000000..dffc399 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/temp-to-perm-process/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a temp to perm process with structured process, quality checks, and system integration +--- + +# Temp To Perm Process + +## Purpose + +Create a comprehensive temp to perm process that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing temp to perm process documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the temp to perm process +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the temp to perm process using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Temp To Perm Process + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/training-needs-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/training-needs-analysis/SKILL.md new file mode 100644 index 0000000..3a5fdbe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/training-needs-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a training needs analysis with structured process, quality checks, and system integration +--- + +# Training Needs Analysis + +## Purpose + +Analyze and produce a comprehensive training needs analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing training needs analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the training needs analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the training needs analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Training Needs Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/training-program-design/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/training-program-design/SKILL.md new file mode 100644 index 0000000..f5297db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/training-program-design/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a training program design with structured process, quality checks, and system integration +--- + +# Training Program Design + +## Purpose + +Create a comprehensive training program design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing training program design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the training program design +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the training program design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Training Program Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/wellness-program/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/wellness-program/SKILL.md new file mode 100644 index 0000000..3a46bae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/wellness-program/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a wellness program with structured process, quality checks, and system integration +--- + +# Wellness Program + +## Purpose + +Design and document a comprehensive wellness program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing wellness program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the wellness program +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the wellness program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Wellness Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/workforce-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/workforce-planning/SKILL.md new file mode 100644 index 0000000..91c206f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/workforce-planning/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a workforce planning with structured process, quality checks, and system integration +--- + +# Workforce Planning + +## Purpose + +Design and document a comprehensive workforce planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workforce planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workforce planning +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workforce planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Workforce Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/hr/workshop-facilitator-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/hr/workshop-facilitator-guide/SKILL.md new file mode 100644 index 0000000..43d0efa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/hr/workshop-facilitator-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a workshop facilitator guide with structured process, quality checks, and system integration +--- + +# Workshop Facilitator Guide + +## Purpose + +Design and document a comprehensive workshop facilitator guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: HR & People + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workshop facilitator guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Competency Model, OKRs for People, 9-Box Grid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workshop facilitator guide +- Identify gaps, opportunities, and risks +- Define success metrics: Time to Fill, Quality of Hire, Employee Engagement Score, Attrition Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workshop facilitator guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Structured interviews with scorecards reduce bias + +## Output Format + +```markdown +# Workshop Facilitator Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Competency Model +- OKRs for People +- 9-Box Grid +- Employee Lifecycle +- Employer Value Proposition +- Total Rewards + +## Key Metrics +- Time to Fill +- Quality of Hire +- Employee Engagement Score +- Attrition Rate +- Offer Acceptance Rate +- Training Completion Rate +- Internal Mobility Rate + +## Best Practices +- Structured interviews with scorecards reduce bias +- Respond to candidates within 48 hours +- 30-60-90 day plans for every new hire +- Regular 1:1s (weekly or biweekly) +- Exit interviews for every departure + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/acceptable-use-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/acceptable-use-policy/SKILL.md new file mode 100644 index 0000000..cf97935 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/acceptable-use-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a acceptable use policy with structured process, quality checks, and system integration +--- + +# Acceptable Use Policy + +## Purpose + +Create a comprehensive acceptable use policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing acceptable use policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the acceptable use policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the acceptable use policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Acceptable Use Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/annual-report-compliance/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/annual-report-compliance/SKILL.md new file mode 100644 index 0000000..3e407a1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/annual-report-compliance/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a annual report compliance with structured process, quality checks, and system integration +--- + +# Annual Report Compliance + +## Purpose + +Analyze and produce a comprehensive annual report compliance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing annual report compliance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the annual report compliance +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the annual report compliance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Annual Report Compliance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/anti-bribery-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/anti-bribery-policy/SKILL.md new file mode 100644 index 0000000..c86683d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/anti-bribery-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a anti bribery policy with structured process, quality checks, and system integration +--- + +# Anti Bribery Policy + +## Purpose + +Create a comprehensive anti bribery policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing anti bribery policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the anti bribery policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the anti bribery policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Anti Bribery Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/audit-response/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/audit-response/SKILL.md new file mode 100644 index 0000000..f51b7c9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/audit-response/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a audit response with structured process, quality checks, and system integration +--- + +# Audit Response + +## Purpose + +Analyze and produce a comprehensive audit response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audit response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audit response +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audit response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Audit Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/board-resolution/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/board-resolution/SKILL.md new file mode 100644 index 0000000..2106e0b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/board-resolution/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a board resolution with structured process, quality checks, and system integration +--- + +# Board Resolution + +## Purpose + +Create a comprehensive board resolution that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board resolution documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board resolution +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board resolution using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Board Resolution + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/breach-notification/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/breach-notification/SKILL.md new file mode 100644 index 0000000..89ee286 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/breach-notification/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a breach notification with structured process, quality checks, and system integration +--- + +# Breach Notification + +## Purpose + +Create a comprehensive breach notification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breach notification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breach notification +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breach notification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Breach Notification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/bylaws-template/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/bylaws-template/SKILL.md new file mode 100644 index 0000000..933a2da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/bylaws-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a bylaws template with structured process, quality checks, and system integration +--- + +# Bylaws Template + +## Purpose + +Create a comprehensive bylaws template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bylaws template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bylaws template +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bylaws template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Bylaws Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/ccpa-compliance-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/ccpa-compliance-checklist/SKILL.md new file mode 100644 index 0000000..fd8d6e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/ccpa-compliance-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a ccpa compliance checklist with structured process, quality checks, and system integration +--- + +# Ccpa Compliance Checklist + +## Purpose + +Analyze and produce a comprehensive ccpa compliance checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ccpa compliance checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ccpa compliance checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ccpa compliance checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Ccpa Compliance Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/cease-and-desist/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/cease-and-desist/SKILL.md new file mode 100644 index 0000000..b79a926 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/cease-and-desist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cease and desist with structured process, quality checks, and system integration +--- + +# Cease And Desist + +## Purpose + +Create a comprehensive cease and desist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cease and desist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cease and desist +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cease and desist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Cease And Desist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/code-of-conduct/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/code-of-conduct/SKILL.md new file mode 100644 index 0000000..e8ccaf1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/code-of-conduct/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a code of conduct with structured process, quality checks, and system integration +--- + +# Code Of Conduct + +## Purpose + +Create a comprehensive code of conduct that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing code of conduct documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the code of conduct +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the code of conduct using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Code Of Conduct + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/compliance-program/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/compliance-program/SKILL.md new file mode 100644 index 0000000..8db3ca8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/compliance-program/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a compliance program with structured process, quality checks, and system integration +--- + +# Compliance Program + +## Purpose + +Design and document a comprehensive compliance program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance program +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Compliance Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/compliance-training-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/compliance-training-outline/SKILL.md new file mode 100644 index 0000000..659a699 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/compliance-training-outline/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a compliance training outline with structured process, quality checks, and system integration +--- + +# Compliance Training Outline + +## Purpose + +Create a comprehensive compliance training outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance training outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance training outline +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance training outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Compliance Training Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/conflict-of-interest-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/conflict-of-interest-policy/SKILL.md new file mode 100644 index 0000000..986c477 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/conflict-of-interest-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a conflict of interest policy with structured process, quality checks, and system integration +--- + +# Conflict Of Interest Policy + +## Purpose + +Create a comprehensive conflict of interest policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conflict of interest policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conflict of interest policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conflict of interest policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Conflict Of Interest Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/consent-resolution/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/consent-resolution/SKILL.md new file mode 100644 index 0000000..dca3183 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/consent-resolution/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a consent resolution with structured process, quality checks, and system integration +--- + +# Consent Resolution + +## Purpose + +Create a comprehensive consent resolution that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing consent resolution documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the consent resolution +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the consent resolution using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Consent Resolution + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/contractor-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/contractor-agreement/SKILL.md new file mode 100644 index 0000000..780d346 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/contractor-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a contractor agreement with structured process, quality checks, and system integration +--- + +# Contractor Agreement + +## Purpose + +Create a comprehensive contractor agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing contractor agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the contractor agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the contractor agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Contractor Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/cookie-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/cookie-policy/SKILL.md new file mode 100644 index 0000000..84db4c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/cookie-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cookie policy with structured process, quality checks, and system integration +--- + +# Cookie Policy + +## Purpose + +Create a comprehensive cookie policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cookie policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cookie policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cookie policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Cookie Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/copyright-notice/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/copyright-notice/SKILL.md new file mode 100644 index 0000000..c9994a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/copyright-notice/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a copyright notice with structured process, quality checks, and system integration +--- + +# Copyright Notice + +## Purpose + +Create a comprehensive copyright notice that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing copyright notice documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the copyright notice +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the copyright notice using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Copyright Notice + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/data-processing-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/data-processing-agreement/SKILL.md new file mode 100644 index 0000000..eee6ead --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/data-processing-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data processing agreement with structured process, quality checks, and system integration +--- + +# Data Processing Agreement + +## Purpose + +Create a comprehensive data processing agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data processing agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data processing agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data processing agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Data Processing Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/data-retention-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/data-retention-policy/SKILL.md new file mode 100644 index 0000000..4c456c5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/data-retention-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a data retention policy with structured process, quality checks, and system integration +--- + +# Data Retention Policy + +## Purpose + +Create a comprehensive data retention policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data retention policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data retention policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data retention policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Data Retention Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/demand-letter/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/demand-letter/SKILL.md new file mode 100644 index 0000000..368276f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/demand-letter/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a demand letter with structured process, quality checks, and system integration +--- + +# Demand Letter + +## Purpose + +Create a comprehensive demand letter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing demand letter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the demand letter +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the demand letter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Demand Letter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/dmca-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/dmca-policy/SKILL.md new file mode 100644 index 0000000..57d7354 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/dmca-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a dmca policy with structured process, quality checks, and system integration +--- + +# Dmca Policy + +## Purpose + +Create a comprehensive dmca policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dmca policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dmca policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dmca policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Dmca Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/dpia-template/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/dpia-template/SKILL.md new file mode 100644 index 0000000..4efba65 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/dpia-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a dpia template with structured process, quality checks, and system integration +--- + +# Dpia Template + +## Purpose + +Create a comprehensive dpia template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dpia template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dpia template +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dpia template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Dpia Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/employment-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/employment-agreement/SKILL.md new file mode 100644 index 0000000..6be2a15 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/employment-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a employment agreement with structured process, quality checks, and system integration +--- + +# Employment Agreement + +## Purpose + +Create a comprehensive employment agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employment agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employment agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employment agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Employment Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/gdpr-compliance-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/gdpr-compliance-audit/SKILL.md new file mode 100644 index 0000000..23f3a01 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/gdpr-compliance-audit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a gdpr compliance audit with structured process, quality checks, and system integration +--- + +# Gdpr Compliance Audit + +## Purpose + +Analyze and produce a comprehensive gdpr compliance audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gdpr compliance audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gdpr compliance audit +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gdpr compliance audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Gdpr Compliance Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/gdpr-data-mapping/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/gdpr-data-mapping/SKILL.md new file mode 100644 index 0000000..ba641bb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/gdpr-data-mapping/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a gdpr data mapping with structured process, quality checks, and system integration +--- + +# Gdpr Data Mapping + +## Purpose + +Create a comprehensive gdpr data mapping that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gdpr data mapping documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gdpr data mapping +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gdpr data mapping using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Gdpr Data Mapping + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/incident-response-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/incident-response-plan/SKILL.md new file mode 100644 index 0000000..421aa9e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/incident-response-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a incident response plan with structured process, quality checks, and system integration +--- + +# Incident Response Plan + +## Purpose + +Design and document a comprehensive incident response plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident response plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident response plan +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident response plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Incident Response Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/insider-trading-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/insider-trading-policy/SKILL.md new file mode 100644 index 0000000..d59e0a1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/insider-trading-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a insider trading policy with structured process, quality checks, and system integration +--- + +# Insider Trading Policy + +## Purpose + +Create a comprehensive insider trading policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing insider trading policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the insider trading policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the insider trading policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Insider Trading Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/insurance-review/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/insurance-review/SKILL.md new file mode 100644 index 0000000..4d96338 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/insurance-review/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a insurance review with structured process, quality checks, and system integration +--- + +# Insurance Review + +## Purpose + +Analyze and produce a comprehensive insurance review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing insurance review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the insurance review +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the insurance review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Insurance Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/ip-assignment-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/ip-assignment-agreement/SKILL.md new file mode 100644 index 0000000..1c3e04d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/ip-assignment-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a ip assignment agreement with structured process, quality checks, and system integration +--- + +# Ip Assignment Agreement + +## Purpose + +Create a comprehensive ip assignment agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ip assignment agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ip assignment agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ip assignment agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Ip Assignment Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/joint-venture-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/joint-venture-agreement/SKILL.md new file mode 100644 index 0000000..5e7cd08 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/joint-venture-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a joint venture agreement with structured process, quality checks, and system integration +--- + +# Joint Venture Agreement + +## Purpose + +Create a comprehensive joint venture agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing joint venture agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the joint venture agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the joint venture agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Joint Venture Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/lease-review-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/lease-review-checklist/SKILL.md new file mode 100644 index 0000000..e742f74 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/lease-review-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a lease review checklist with structured process, quality checks, and system integration +--- + +# Lease Review Checklist + +## Purpose + +Analyze and produce a comprehensive lease review checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lease review checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lease review checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lease review checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Lease Review Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/licensing-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/licensing-agreement/SKILL.md new file mode 100644 index 0000000..ae6fa56 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/licensing-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a licensing agreement with structured process, quality checks, and system integration +--- + +# Licensing Agreement + +## Purpose + +Create a comprehensive licensing agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing licensing agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the licensing agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the licensing agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Licensing Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/litigation-hold/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/litigation-hold/SKILL.md new file mode 100644 index 0000000..1d513b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/litigation-hold/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a litigation hold with structured process, quality checks, and system integration +--- + +# Litigation Hold + +## Purpose + +Create a comprehensive litigation hold that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing litigation hold documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the litigation hold +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the litigation hold using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Litigation Hold + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/meeting-minutes/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/meeting-minutes/SKILL.md new file mode 100644 index 0000000..40644d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/meeting-minutes/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a meeting minutes with structured process, quality checks, and system integration +--- + +# Meeting Minutes + +## Purpose + +Create a comprehensive meeting minutes that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting minutes documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting minutes +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting minutes using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Meeting Minutes + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/mou-template/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/mou-template/SKILL.md new file mode 100644 index 0000000..b09a85a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/mou-template/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a mou template with structured process, quality checks, and system integration +--- + +# Mou Template + +## Purpose + +Create a comprehensive mou template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mou template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mou template +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mou template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Mou Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/nda-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/nda-generator/SKILL.md new file mode 100644 index 0000000..e9d21da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/nda-generator/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a nda generator with structured process, quality checks, and system integration +--- + +# Nda Generator + +## Purpose + +Create a comprehensive nda generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nda generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nda generator +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nda generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Nda Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/offer-letter/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/offer-letter/SKILL.md new file mode 100644 index 0000000..08931ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/offer-letter/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a offer letter with structured process, quality checks, and system integration +--- + +# Offer Letter + +## Purpose + +Create a comprehensive offer letter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing offer letter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the offer letter +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the offer letter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Offer Letter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/operating-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/operating-agreement/SKILL.md new file mode 100644 index 0000000..6b8cfe8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/operating-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a operating agreement with structured process, quality checks, and system integration +--- + +# Operating Agreement + +## Purpose + +Create a comprehensive operating agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing operating agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the operating agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the operating agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Operating Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/partnership-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/partnership-agreement/SKILL.md new file mode 100644 index 0000000..089d78b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/partnership-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a partnership agreement with structured process, quality checks, and system integration +--- + +# Partnership Agreement + +## Purpose + +Create a comprehensive partnership agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing partnership agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the partnership agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the partnership agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Partnership Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/patent-prior-art-search/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/patent-prior-art-search/SKILL.md new file mode 100644 index 0000000..6a0f898 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/patent-prior-art-search/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a patent prior art search with structured process, quality checks, and system integration +--- + +# Patent Prior Art Search + +## Purpose + +Create a comprehensive patent prior art search that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing patent prior art search documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the patent prior art search +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the patent prior art search using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Patent Prior Art Search + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/privacy-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/privacy-policy/SKILL.md new file mode 100644 index 0000000..d80a835 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/privacy-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a privacy policy with structured process, quality checks, and system integration +--- + +# Privacy Policy + +## Purpose + +Create a comprehensive privacy policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing privacy policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the privacy policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the privacy policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Privacy Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/refund-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/refund-policy/SKILL.md new file mode 100644 index 0000000..70d4844 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/refund-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a refund policy with structured process, quality checks, and system integration +--- + +# Refund Policy + +## Purpose + +Create a comprehensive refund policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing refund policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the refund policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the refund policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Refund Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/regulatory-change-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/regulatory-change-tracker/SKILL.md new file mode 100644 index 0000000..30fa2f5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/regulatory-change-tracker/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a regulatory change tracker with structured process, quality checks, and system integration +--- + +# Regulatory Change Tracker + +## Purpose + +Analyze and produce a comprehensive regulatory change tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing regulatory change tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the regulatory change tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the regulatory change tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Regulatory Change Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/regulatory-filing-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/regulatory-filing-checklist/SKILL.md new file mode 100644 index 0000000..0f1c5d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/regulatory-filing-checklist/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a regulatory filing checklist with structured process, quality checks, and system integration +--- + +# Regulatory Filing Checklist + +## Purpose + +Analyze and produce a comprehensive regulatory filing checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing regulatory filing checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the regulatory filing checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the regulatory filing checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Regulatory Filing Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/risk-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/risk-assessment/SKILL.md new file mode 100644 index 0000000..913362d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/risk-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a risk assessment with structured process, quality checks, and system integration +--- + +# Risk Assessment + +## Purpose + +Analyze and produce a comprehensive risk assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing risk assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the risk assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the risk assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Risk Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/service-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/service-agreement/SKILL.md new file mode 100644 index 0000000..6d9a5d9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/service-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a service agreement with structured process, quality checks, and system integration +--- + +# Service Agreement + +## Purpose + +Create a comprehensive service agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing service agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the service agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the service agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Service Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/settlement-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/settlement-agreement/SKILL.md new file mode 100644 index 0000000..8fd6695 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/settlement-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a settlement agreement with structured process, quality checks, and system integration +--- + +# Settlement Agreement + +## Purpose + +Create a comprehensive settlement agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing settlement agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the settlement agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the settlement agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Settlement Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/shareholder-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/shareholder-agreement/SKILL.md new file mode 100644 index 0000000..972c685 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/shareholder-agreement/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a shareholder agreement with structured process, quality checks, and system integration +--- + +# Shareholder Agreement + +## Purpose + +Create a comprehensive shareholder agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing shareholder agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the shareholder agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the shareholder agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Shareholder Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/shipping-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/shipping-policy/SKILL.md new file mode 100644 index 0000000..8b50067 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/shipping-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a shipping policy with structured process, quality checks, and system integration +--- + +# Shipping Policy + +## Purpose + +Create a comprehensive shipping policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing shipping policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the shipping policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the shipping policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Shipping Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/termination-letter/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/termination-letter/SKILL.md new file mode 100644 index 0000000..52bebe9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/termination-letter/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a termination letter with structured process, quality checks, and system integration +--- + +# Termination Letter + +## Purpose + +Create a comprehensive termination letter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing termination letter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the termination letter +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the termination letter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Termination Letter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/terms-of-service/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/terms-of-service/SKILL.md new file mode 100644 index 0000000..c8c5bb8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/terms-of-service/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a terms of service with structured process, quality checks, and system integration +--- + +# Terms Of Service + +## Purpose + +Create a comprehensive terms of service that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing terms of service documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the terms of service +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the terms of service using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Terms Of Service + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/trademark-filing-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/trademark-filing-guide/SKILL.md new file mode 100644 index 0000000..8c634a9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/trademark-filing-guide/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a trademark filing guide with structured process, quality checks, and system integration +--- + +# Trademark Filing Guide + +## Purpose + +Design and document a comprehensive trademark filing guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trademark filing guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trademark filing guide +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trademark filing guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Trademark Filing Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/vendor-contract-review/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/vendor-contract-review/SKILL.md new file mode 100644 index 0000000..b02b136 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/vendor-contract-review/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a vendor contract review with structured process, quality checks, and system integration +--- + +# Vendor Contract Review + +## Purpose + +Analyze and produce a comprehensive vendor contract review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor contract review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor contract review +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor contract review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Vendor Contract Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/legal/whistleblower-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/legal/whistleblower-policy/SKILL.md new file mode 100644 index 0000000..5dcbb45 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/legal/whistleblower-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a whistleblower policy with structured process, quality checks, and system integration +--- + +# Whistleblower Policy + +## Purpose + +Create a comprehensive whistleblower policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Legal & Compliance + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Parties Involved**: Who the agreement is between + +### Optional +- **Jurisdiction**: Applicable legal jurisdiction +- **Specific Terms**: Any pre-negotiated terms to include + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing whistleblower policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Contract Lifecycle Management, Risk Assessment Matrix, Compliance Framework + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the whistleblower policy +- Identify gaps, opportunities, and risks +- Define success metrics: Contract Cycle Time, Compliance Score, Open Risk Items, Policy Acknowledgment Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the whistleblower policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Always include limitation of liability + +## Output Format + +```markdown +# Whistleblower Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Contract Lifecycle Management +- Risk Assessment Matrix +- Compliance Framework +- Data Protection by Design +- Three Lines of Defense + +## Key Metrics +- Contract Cycle Time +- Compliance Score +- Open Risk Items +- Policy Acknowledgment Rate +- Incident Response Time + +## Best Practices +- Always include limitation of liability +- Define all key terms in a definitions section +- Use plain language wherever possible +- Version control all legal documents +- Review and update policies annually +- DISCLAIMER: Skills provide templates and frameworks only — always have a qualified attorney review before use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/account-based-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/account-based-marketing/SKILL.md new file mode 100644 index 0000000..34e5019 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/account-based-marketing/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a account based marketing with structured process, quality checks, and system integration +--- + +# Account Based Marketing + +## Purpose + +Create a comprehensive account based marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing account based marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the account based marketing +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the account based marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Account Based Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/attribution-model/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/attribution-model/SKILL.md new file mode 100644 index 0000000..d33c0db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/attribution-model/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a attribution model with structured process, quality checks, and system integration +--- + +# Attribution Model + +## Purpose + +Design and document a comprehensive attribution model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing attribution model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the attribution model +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the attribution model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Attribution Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/audience-persona/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/audience-persona/SKILL.md new file mode 100644 index 0000000..06dc763 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/audience-persona/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a audience persona with structured process, quality checks, and system integration +--- + +# Audience Persona + +## Purpose + +Create a comprehensive audience persona that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audience persona documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audience persona +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audience persona using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Audience Persona + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/audience-segmentation/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/audience-segmentation/SKILL.md new file mode 100644 index 0000000..2cba92d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/audience-segmentation/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a audience segmentation with structured process, quality checks, and system integration +--- + +# Audience Segmentation + +## Purpose + +Create a comprehensive audience segmentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audience segmentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audience segmentation +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audience segmentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Audience Segmentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/b2b-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/b2b-marketing-plan/SKILL.md new file mode 100644 index 0000000..fdd0944 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/b2b-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a b2b marketing plan with structured process, quality checks, and system integration +--- + +# B2b Marketing Plan + +## Purpose + +Design and document a comprehensive b2b marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing b2b marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the b2b marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the b2b marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# B2b Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/b2c-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/b2c-marketing-plan/SKILL.md new file mode 100644 index 0000000..a8d8081 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/b2c-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a b2c marketing plan with structured process, quality checks, and system integration +--- + +# B2c Marketing Plan + +## Purpose + +Design and document a comprehensive b2c marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing b2c marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the b2c marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the b2c marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# B2c Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/back-to-school-campaign/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/back-to-school-campaign/SKILL.md new file mode 100644 index 0000000..543aefe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/back-to-school-campaign/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a back to school campaign with structured process, quality checks, and system integration +--- + +# Back To School Campaign + +## Purpose + +Design and document a comprehensive back to school campaign that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing back to school campaign documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the back to school campaign +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the back to school campaign using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Back To School Campaign + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/brand-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/brand-audit/SKILL.md new file mode 100644 index 0000000..944303c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/brand-audit/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a brand audit with structured process, quality checks, and system integration +--- + +# Brand Audit + +## Purpose + +Analyze and produce a comprehensive brand audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand audit +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Brand Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/brand-guidelines/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/brand-guidelines/SKILL.md new file mode 100644 index 0000000..5698c80 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/brand-guidelines/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a brand guidelines with structured process, quality checks, and system integration +--- + +# Brand Guidelines + +## Purpose + +Design and document a comprehensive brand guidelines that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand guidelines documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand guidelines +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand guidelines using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Brand Guidelines + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/brand-messaging-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/brand-messaging-framework/SKILL.md new file mode 100644 index 0000000..75f2f78 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/brand-messaging-framework/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a brand messaging framework with structured process, quality checks, and system integration +--- + +# Brand Messaging Framework + +## Purpose + +Design and document a comprehensive brand messaging framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand messaging framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand messaging framework +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand messaging framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Brand Messaging Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/brand-positioning/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/brand-positioning/SKILL.md new file mode 100644 index 0000000..4c2c2aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/brand-positioning/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a brand positioning with structured process, quality checks, and system integration +--- + +# Brand Positioning + +## Purpose + +Create a comprehensive brand positioning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand positioning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand positioning +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand positioning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Brand Positioning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/brand-voice-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/brand-voice-guide/SKILL.md new file mode 100644 index 0000000..9428eec --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/brand-voice-guide/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a brand voice guide with structured process, quality checks, and system integration +--- + +# Brand Voice Guide + +## Purpose + +Design and document a comprehensive brand voice guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand voice guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand voice guide +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand voice guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Brand Voice Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/campaign-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/campaign-brief/SKILL.md new file mode 100644 index 0000000..a12fffe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/campaign-brief/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a campaign brief with structured process, quality checks, and system integration +--- + +# Campaign Brief + +## Purpose + +Create a comprehensive campaign brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing campaign brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the campaign brief +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the campaign brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Campaign Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/campaign-retrospective/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/campaign-retrospective/SKILL.md new file mode 100644 index 0000000..a4955d3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/campaign-retrospective/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a campaign retrospective with structured process, quality checks, and system integration +--- + +# Campaign Retrospective + +## Purpose + +Design and document a comprehensive campaign retrospective that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing campaign retrospective documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the campaign retrospective +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the campaign retrospective using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Campaign Retrospective + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/campaign-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/campaign-strategy/SKILL.md new file mode 100644 index 0000000..6f84c7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/campaign-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a campaign strategy with structured process, quality checks, and system integration +--- + +# Campaign Strategy + +## Purpose + +Design and document a comprehensive campaign strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing campaign strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the campaign strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the campaign strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Campaign Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/channel-mix-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/channel-mix-optimization/SKILL.md new file mode 100644 index 0000000..eb1bc4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/channel-mix-optimization/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a channel mix optimization with structured process, quality checks, and system integration +--- + +# Channel Mix Optimization + +## Purpose + +Create a comprehensive channel mix optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing channel mix optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the channel mix optimization +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the channel mix optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Channel Mix Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/channel-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/channel-strategy/SKILL.md new file mode 100644 index 0000000..6921bba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/channel-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a channel strategy with structured process, quality checks, and system integration +--- + +# Channel Strategy + +## Purpose + +Design and document a comprehensive channel strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing channel strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the channel strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the channel strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Channel Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/co-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/co-marketing-plan/SKILL.md new file mode 100644 index 0000000..da60f15 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/co-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a co marketing plan with structured process, quality checks, and system integration +--- + +# Co Marketing Plan + +## Purpose + +Design and document a comprehensive co marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing co marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the co marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the co marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Co Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/community-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/community-strategy/SKILL.md new file mode 100644 index 0000000..76dfc8f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/community-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a community strategy with structured process, quality checks, and system integration +--- + +# Community Strategy + +## Purpose + +Design and document a comprehensive community strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing community strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the community strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the community strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Community Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/competitor-ad-teardown/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/competitor-ad-teardown/SKILL.md new file mode 100644 index 0000000..c2110ff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/competitor-ad-teardown/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a competitor ad teardown with structured process, quality checks, and system integration +--- + +# Competitor Ad Teardown + +## Purpose + +Analyze and produce a comprehensive competitor ad teardown that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitor ad teardown documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitor ad teardown +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitor ad teardown using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Competitor Ad Teardown + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/competitor-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/competitor-analysis/SKILL.md new file mode 100644 index 0000000..a5000b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/competitor-analysis/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a competitor analysis with structured process, quality checks, and system integration +--- + +# Competitor Analysis + +## Purpose + +Analyze and produce a comprehensive competitor analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitor analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitor analysis +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitor analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Competitor Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/content-marketing-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/content-marketing-strategy/SKILL.md new file mode 100644 index 0000000..23c0875 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/content-marketing-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a content marketing strategy with structured process, quality checks, and system integration +--- + +# Content Marketing Strategy + +## Purpose + +Design and document a comprehensive content marketing strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content marketing strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content marketing strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content marketing strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Content Marketing Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/conversion-funnel-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/conversion-funnel-analysis/SKILL.md new file mode 100644 index 0000000..0d2dfe0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/conversion-funnel-analysis/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a conversion funnel analysis with structured process, quality checks, and system integration +--- + +# Conversion Funnel Analysis + +## Purpose + +Analyze and produce a comprehensive conversion funnel analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conversion funnel analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conversion funnel analysis +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conversion funnel analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Conversion Funnel Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/crisis-communication-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/crisis-communication-plan/SKILL.md new file mode 100644 index 0000000..d07be50 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/crisis-communication-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a crisis communication plan with structured process, quality checks, and system integration +--- + +# Crisis Communication Plan + +## Purpose + +Design and document a comprehensive crisis communication plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crisis communication plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crisis communication plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crisis communication plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Crisis Communication Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/cross-promotion-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/cross-promotion-strategy/SKILL.md new file mode 100644 index 0000000..032e649 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/cross-promotion-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a cross promotion strategy with structured process, quality checks, and system integration +--- + +# Cross Promotion Strategy + +## Purpose + +Design and document a comprehensive cross promotion strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross promotion strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross promotion strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross promotion strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Cross Promotion Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/customer-journey-map/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/customer-journey-map/SKILL.md new file mode 100644 index 0000000..3ea9c3a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/customer-journey-map/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a customer journey map with structured process, quality checks, and system integration +--- + +# Customer Journey Map + +## Purpose + +Create a comprehensive customer journey map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer journey map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer journey map +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer journey map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Customer Journey Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/d2c-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/d2c-strategy/SKILL.md new file mode 100644 index 0000000..41a900a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/d2c-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a d2c strategy with structured process, quality checks, and system integration +--- + +# D2c Strategy + +## Purpose + +Design and document a comprehensive d2c strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing d2c strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the d2c strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the d2c strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# D2c Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/demand-generation/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/demand-generation/SKILL.md new file mode 100644 index 0000000..03b1e7a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/demand-generation/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a demand generation with structured process, quality checks, and system integration +--- + +# Demand Generation + +## Purpose + +Create a comprehensive demand generation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing demand generation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the demand generation +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the demand generation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Demand Generation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/drip-campaign-design/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/drip-campaign-design/SKILL.md new file mode 100644 index 0000000..5b4a202 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/drip-campaign-design/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a drip campaign design with structured process, quality checks, and system integration +--- + +# Drip Campaign Design + +## Purpose + +Create a comprehensive drip campaign design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing drip campaign design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the drip campaign design +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the drip campaign design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Drip Campaign Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/elevator-pitch/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/elevator-pitch/SKILL.md new file mode 100644 index 0000000..70129ff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/elevator-pitch/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a elevator pitch with structured process, quality checks, and system integration +--- + +# Elevator Pitch + +## Purpose + +Create a comprehensive elevator pitch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing elevator pitch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the elevator pitch +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the elevator pitch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Elevator Pitch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/event-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/event-marketing-plan/SKILL.md new file mode 100644 index 0000000..1e90f7f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/event-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a event marketing plan with structured process, quality checks, and system integration +--- + +# Event Marketing Plan + +## Purpose + +Design and document a comprehensive event marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Event Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/geo-targeting-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/geo-targeting-strategy/SKILL.md new file mode 100644 index 0000000..e33624f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/geo-targeting-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a geo targeting strategy with structured process, quality checks, and system integration +--- + +# Geo Targeting Strategy + +## Purpose + +Design and document a comprehensive geo targeting strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing geo targeting strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the geo targeting strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the geo targeting strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Geo Targeting Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/go-to-market-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/go-to-market-plan/SKILL.md new file mode 100644 index 0000000..f6dc7d6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/go-to-market-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a go to market plan with structured process, quality checks, and system integration +--- + +# Go To Market Plan + +## Purpose + +Design and document a comprehensive go to market plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing go to market plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the go to market plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the go to market plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Go To Market Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/growth-experiment/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/growth-experiment/SKILL.md new file mode 100644 index 0000000..c389f44 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/growth-experiment/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a growth experiment with structured process, quality checks, and system integration +--- + +# Growth Experiment + +## Purpose + +Create a comprehensive growth experiment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing growth experiment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the growth experiment +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the growth experiment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Growth Experiment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/guerrilla-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/guerrilla-marketing/SKILL.md new file mode 100644 index 0000000..b1776e1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/guerrilla-marketing/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a guerrilla marketing with structured process, quality checks, and system integration +--- + +# Guerrilla Marketing + +## Purpose + +Create a comprehensive guerrilla marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing guerrilla marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the guerrilla marketing +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the guerrilla marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Guerrilla Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/holiday-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/holiday-marketing-plan/SKILL.md new file mode 100644 index 0000000..fc782e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/holiday-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a holiday marketing plan with structured process, quality checks, and system integration +--- + +# Holiday Marketing Plan + +## Purpose + +Design and document a comprehensive holiday marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing holiday marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the holiday marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the holiday marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Holiday Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/influencer-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/influencer-brief/SKILL.md new file mode 100644 index 0000000..e773eda --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/influencer-brief/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a influencer brief with structured process, quality checks, and system integration +--- + +# Influencer Brief + +## Purpose + +Create a comprehensive influencer brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing influencer brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the influencer brief +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the influencer brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Influencer Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/influencer-outreach/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/influencer-outreach/SKILL.md new file mode 100644 index 0000000..942fe37 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/influencer-outreach/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a influencer outreach with structured process, quality checks, and system integration +--- + +# Influencer Outreach + +## Purpose + +Create a comprehensive influencer outreach that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing influencer outreach documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the influencer outreach +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the influencer outreach using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Influencer Outreach + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/influencer-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/influencer-strategy/SKILL.md new file mode 100644 index 0000000..e6ddb82 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/influencer-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a influencer strategy with structured process, quality checks, and system integration +--- + +# Influencer Strategy + +## Purpose + +Design and document a comprehensive influencer strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing influencer strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the influencer strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the influencer strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Influencer Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/kpi-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/kpi-framework/SKILL.md new file mode 100644 index 0000000..b317d21 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/kpi-framework/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a kpi framework with structured process, quality checks, and system integration +--- + +# Kpi Framework + +## Purpose + +Design and document a comprehensive kpi framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kpi framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kpi framework +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kpi framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Kpi Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/launch-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/launch-checklist/SKILL.md new file mode 100644 index 0000000..d8ec4c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/launch-checklist/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a launch checklist with structured process, quality checks, and system integration +--- + +# Launch Checklist + +## Purpose + +Analyze and produce a comprehensive launch checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing launch checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the launch checklist +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the launch checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Launch Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/launch-timeline/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/launch-timeline/SKILL.md new file mode 100644 index 0000000..661872c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/launch-timeline/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a launch timeline with structured process, quality checks, and system integration +--- + +# Launch Timeline + +## Purpose + +Create a comprehensive launch timeline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing launch timeline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the launch timeline +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the launch timeline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Launch Timeline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/lead-magnet-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/lead-magnet-strategy/SKILL.md new file mode 100644 index 0000000..aca1c18 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/lead-magnet-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a lead magnet strategy with structured process, quality checks, and system integration +--- + +# Lead Magnet Strategy + +## Purpose + +Design and document a comprehensive lead magnet strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lead magnet strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lead magnet strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lead magnet strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Lead Magnet Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/local-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/local-marketing-plan/SKILL.md new file mode 100644 index 0000000..43827ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/local-marketing-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a local marketing plan with structured process, quality checks, and system integration +--- + +# Local Marketing Plan + +## Purpose + +Design and document a comprehensive local marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Local Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/loyalty-program/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/loyalty-program/SKILL.md new file mode 100644 index 0000000..99a1da1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/loyalty-program/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a loyalty program with structured process, quality checks, and system integration +--- + +# Loyalty Program + +## Purpose + +Design and document a comprehensive loyalty program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing loyalty program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the loyalty program +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the loyalty program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Loyalty Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/market-research/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/market-research/SKILL.md new file mode 100644 index 0000000..dd80a0e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/market-research/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a market research with structured process, quality checks, and system integration +--- + +# Market Research + +## Purpose + +Create a comprehensive market research that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market research documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market research +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market research using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Market Research + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/market-sizing/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/market-sizing/SKILL.md new file mode 100644 index 0000000..87b91b1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/market-sizing/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a market sizing with structured process, quality checks, and system integration +--- + +# Market Sizing + +## Purpose + +Analyze and produce a comprehensive market sizing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market sizing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market sizing +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market sizing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Market Sizing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-automation-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-automation-setup/SKILL.md new file mode 100644 index 0000000..a6dafb4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-automation-setup/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a marketing automation setup with structured process, quality checks, and system integration +--- + +# Marketing Automation Setup + +## Purpose + +Design and document a comprehensive marketing automation setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing automation setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing automation setup +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing automation setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Automation Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-budget/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-budget/SKILL.md new file mode 100644 index 0000000..d9a109e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-budget/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a marketing budget with structured process, quality checks, and system integration +--- + +# Marketing Budget + +## Purpose + +Create a comprehensive marketing budget that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing budget documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing budget +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing budget using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Budget + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-calendar/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-calendar/SKILL.md new file mode 100644 index 0000000..ba06e8c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-calendar/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a marketing calendar with structured process, quality checks, and system integration +--- + +# Marketing Calendar + +## Purpose + +Design and document a comprehensive marketing calendar that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing calendar documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing calendar +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing calendar using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Calendar + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-dashboard/SKILL.md new file mode 100644 index 0000000..4a41a25 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-dashboard/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a marketing dashboard with structured process, quality checks, and system integration +--- + +# Marketing Dashboard + +## Purpose + +Analyze and produce a comprehensive marketing dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-funnel-design/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-funnel-design/SKILL.md new file mode 100644 index 0000000..68883b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-funnel-design/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a marketing funnel design with structured process, quality checks, and system integration +--- + +# Marketing Funnel Design + +## Purpose + +Create a comprehensive marketing funnel design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing funnel design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing funnel design +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing funnel design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Funnel Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/marketing-stack-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/marketing-stack-audit/SKILL.md new file mode 100644 index 0000000..313a58c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/marketing-stack-audit/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a marketing stack audit with structured process, quality checks, and system integration +--- + +# Marketing Stack Audit + +## Purpose + +Analyze and produce a comprehensive marketing stack audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketing stack audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketing stack audit +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketing stack audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Marketing Stack Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/martech-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/martech-evaluation/SKILL.md new file mode 100644 index 0000000..c631659 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/martech-evaluation/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a martech evaluation with structured process, quality checks, and system integration +--- + +# Martech Evaluation + +## Purpose + +Analyze and produce a comprehensive martech evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing martech evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the martech evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the martech evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Martech Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/media-kit/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/media-kit/SKILL.md new file mode 100644 index 0000000..2fc914e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/media-kit/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a media kit with structured process, quality checks, and system integration +--- + +# Media Kit + +## Purpose + +Create a comprehensive media kit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing media kit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the media kit +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the media kit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Media Kit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/media-pitch/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/media-pitch/SKILL.md new file mode 100644 index 0000000..5bdff5d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/media-pitch/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a media pitch with structured process, quality checks, and system integration +--- + +# Media Pitch + +## Purpose + +Create a comprehensive media pitch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing media pitch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the media pitch +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the media pitch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Media Pitch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/messaging-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/messaging-matrix/SKILL.md new file mode 100644 index 0000000..25e8a5e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/messaging-matrix/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a messaging matrix with structured process, quality checks, and system integration +--- + +# Messaging Matrix + +## Purpose + +Create a comprehensive messaging matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing messaging matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the messaging matrix +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the messaging matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Messaging Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/multi-market-launch/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/multi-market-launch/SKILL.md new file mode 100644 index 0000000..2ef7a19 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/multi-market-launch/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a multi market launch with structured process, quality checks, and system integration +--- + +# Multi Market Launch + +## Purpose + +Create a comprehensive multi market launch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing multi market launch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the multi market launch +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the multi market launch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Multi Market Launch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/partnership-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/partnership-strategy/SKILL.md new file mode 100644 index 0000000..fa1344b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/partnership-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a partnership strategy with structured process, quality checks, and system integration +--- + +# Partnership Strategy + +## Purpose + +Design and document a comprehensive partnership strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing partnership strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the partnership strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the partnership strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Partnership Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/pr-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/pr-strategy/SKILL.md new file mode 100644 index 0000000..42451b9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/pr-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a pr strategy with structured process, quality checks, and system integration +--- + +# Pr Strategy + +## Purpose + +Design and document a comprehensive pr strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pr strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pr strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pr strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Pr Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/press-release/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/press-release/SKILL.md new file mode 100644 index 0000000..8279a2e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/press-release/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a press release with structured process, quality checks, and system integration +--- + +# Press Release + +## Purpose + +Create a comprehensive press release that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing press release documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the press release +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the press release using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Press Release + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/product-launch-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/product-launch-plan/SKILL.md new file mode 100644 index 0000000..68aa048 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/product-launch-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a product launch plan with structured process, quality checks, and system integration +--- + +# Product Launch Plan + +## Purpose + +Design and document a comprehensive product launch plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product launch plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product launch plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product launch plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Product Launch Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/rebranding-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/rebranding-plan/SKILL.md new file mode 100644 index 0000000..a45d602 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/rebranding-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a rebranding plan with structured process, quality checks, and system integration +--- + +# Rebranding Plan + +## Purpose + +Design and document a comprehensive rebranding plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rebranding plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rebranding plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rebranding plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Rebranding Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/referral-program/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/referral-program/SKILL.md new file mode 100644 index 0000000..b5acb3a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/referral-program/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a referral program with structured process, quality checks, and system integration +--- + +# Referral Program + +## Purpose + +Design and document a comprehensive referral program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral program +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Referral Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/retargeting-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/retargeting-strategy/SKILL.md new file mode 100644 index 0000000..0a56e14 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/retargeting-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a retargeting strategy with structured process, quality checks, and system integration +--- + +# Retargeting Strategy + +## Purpose + +Design and document a comprehensive retargeting strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retargeting strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retargeting strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retargeting strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Retargeting Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/seasonal-campaign/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/seasonal-campaign/SKILL.md new file mode 100644 index 0000000..bc870a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/seasonal-campaign/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a seasonal campaign with structured process, quality checks, and system integration +--- + +# Seasonal Campaign + +## Purpose + +Design and document a comprehensive seasonal campaign that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seasonal campaign documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seasonal campaign +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seasonal campaign using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Seasonal Campaign + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/sponsorship-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/sponsorship-proposal/SKILL.md new file mode 100644 index 0000000..b7f03ea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/sponsorship-proposal/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a sponsorship proposal with structured process, quality checks, and system integration +--- + +# Sponsorship Proposal + +## Purpose + +Create a comprehensive sponsorship proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sponsorship proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sponsorship proposal +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sponsorship proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Sponsorship Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/tagline-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/tagline-generator/SKILL.md new file mode 100644 index 0000000..3c6c32b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/tagline-generator/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a tagline generator with structured process, quality checks, and system integration +--- + +# Tagline Generator + +## Purpose + +Create a comprehensive tagline generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tagline generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tagline generator +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tagline generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Tagline Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/thought-leadership-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/thought-leadership-plan/SKILL.md new file mode 100644 index 0000000..0aa3255 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/thought-leadership-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a thought leadership plan with structured process, quality checks, and system integration +--- + +# Thought Leadership Plan + +## Purpose + +Design and document a comprehensive thought leadership plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing thought leadership plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the thought leadership plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the thought leadership plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Thought Leadership Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/touchpoint-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/touchpoint-audit/SKILL.md new file mode 100644 index 0000000..fd37898 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/touchpoint-audit/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a touchpoint audit with structured process, quality checks, and system integration +--- + +# Touchpoint Audit + +## Purpose + +Analyze and produce a comprehensive touchpoint audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing touchpoint audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the touchpoint audit +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the touchpoint audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Touchpoint Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/trade-show-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/trade-show-strategy/SKILL.md new file mode 100644 index 0000000..2cfb3ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/trade-show-strategy/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a trade show strategy with structured process, quality checks, and system integration +--- + +# Trade Show Strategy + +## Purpose + +Design and document a comprehensive trade show strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trade show strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trade show strategy +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trade show strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Trade Show Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/unique-selling-proposition/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/unique-selling-proposition/SKILL.md new file mode 100644 index 0000000..79cca5b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/unique-selling-proposition/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a unique selling proposition with structured process, quality checks, and system integration +--- + +# Unique Selling Proposition + +## Purpose + +Create a comprehensive unique selling proposition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing unique selling proposition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the unique selling proposition +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the unique selling proposition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Unique Selling Proposition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/value-proposition-canvas/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/value-proposition-canvas/SKILL.md new file mode 100644 index 0000000..d48fff2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/value-proposition-canvas/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a value proposition canvas with structured process, quality checks, and system integration +--- + +# Value Proposition Canvas + +## Purpose + +Create a comprehensive value proposition canvas that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing value proposition canvas documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the value proposition canvas +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the value proposition canvas using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Value Proposition Canvas + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/vendor-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/vendor-comparison/SKILL.md new file mode 100644 index 0000000..0d19b9f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/vendor-comparison/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Analyze and produce a vendor comparison with structured process, quality checks, and system integration +--- + +# Vendor Comparison + +## Purpose + +Analyze and produce a comprehensive vendor comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor comparison +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Vendor Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/viral-loop-design/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/viral-loop-design/SKILL.md new file mode 100644 index 0000000..6d830bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/viral-loop-design/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Create a viral loop design with structured process, quality checks, and system integration +--- + +# Viral Loop Design + +## Purpose + +Create a comprehensive viral loop design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing viral loop design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the viral loop design +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the viral loop design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Viral Loop Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/marketing/webinar-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/marketing/webinar-plan/SKILL.md new file mode 100644 index 0000000..a41777b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/marketing/webinar-plan/SKILL.md @@ -0,0 +1,138 @@ +--- +description: Design and document a webinar plan with structured process, quality checks, and system integration +--- + +# Webinar Plan + +## Purpose + +Design and document a comprehensive webinar plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Marketing & Advertising + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing webinar plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: AIDA, STP (Segmentation, Targeting, Positioning), Marketing Mix (4Ps/7Ps) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the webinar plan +- Identify gaps, opportunities, and risks +- Define success metrics: CAC, LTV, ROAS, CPM +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the webinar plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Test one variable at a time + +## Output Format + +```markdown +# Webinar Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- AIDA +- STP (Segmentation, Targeting, Positioning) +- Marketing Mix (4Ps/7Ps) +- Customer Journey Mapping +- Jobs To Be Done +- Brand Positioning Canvas +- Ansoff Matrix +- BCG Matrix + +## Key Metrics +- CAC +- LTV +- ROAS +- CPM +- CPC +- CTR +- Conversion Rate +- Brand Awareness +- NPS +- Share of Voice + +## Best Practices +- Test one variable at a time +- Set baselines before optimizing +- Budget allocation: 70% proven / 20% experimental / 10% moonshot +- Review performance weekly, strategy monthly +- Document all campaign learnings + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/advertising-rate-card/SKILL.md b/clowdex-download/.claude/.claude/skills/media/advertising-rate-card/SKILL.md new file mode 100644 index 0000000..bfe5715 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/advertising-rate-card/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a advertising rate card with structured process, quality checks, and system integration +--- + +# Advertising Rate Card + +## Purpose + +Create a comprehensive advertising rate card that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing advertising rate card documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the advertising rate card +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the advertising rate card using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Advertising Rate Card + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/article-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/media/article-outline/SKILL.md new file mode 100644 index 0000000..bb93651 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/article-outline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a article outline with structured process, quality checks, and system integration +--- + +# Article Outline + +## Purpose + +Create a comprehensive article outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing article outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the article outline +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the article outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Article Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/audience-growth-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/media/audience-growth-strategy/SKILL.md new file mode 100644 index 0000000..9a1dd45 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/audience-growth-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a audience growth strategy with structured process, quality checks, and system integration +--- + +# Audience Growth Strategy + +## Purpose + +Design and document a comprehensive audience growth strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audience growth strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audience growth strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audience growth strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Audience Growth Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/audience-insights/SKILL.md b/clowdex-download/.claude/.claude/skills/media/audience-insights/SKILL.md new file mode 100644 index 0000000..0989888 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/audience-insights/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a audience insights with structured process, quality checks, and system integration +--- + +# Audience Insights + +## Purpose + +Create a comprehensive audience insights that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audience insights documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audience insights +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audience insights using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Audience Insights + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/book-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/media/book-outline/SKILL.md new file mode 100644 index 0000000..6a19101 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/book-outline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a book outline with structured process, quality checks, and system integration +--- + +# Book Outline + +## Purpose + +Create a comprehensive book outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing book outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the book outline +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the book outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Book Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/book-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/media/book-proposal/SKILL.md new file mode 100644 index 0000000..8fb383b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/book-proposal/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a book proposal with structured process, quality checks, and system integration +--- + +# Book Proposal + +## Purpose + +Create a comprehensive book proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing book proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the book proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the book proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Book Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/breaking-news-protocol/SKILL.md b/clowdex-download/.claude/.claude/skills/media/breaking-news-protocol/SKILL.md new file mode 100644 index 0000000..9dd7aa5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/breaking-news-protocol/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a breaking news protocol with structured process, quality checks, and system integration +--- + +# Breaking News Protocol + +## Purpose + +Create a comprehensive breaking news protocol that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breaking news protocol documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breaking news protocol +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breaking news protocol using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Breaking News Protocol + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/chapter-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/media/chapter-outline/SKILL.md new file mode 100644 index 0000000..7db6edc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/chapter-outline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a chapter outline with structured process, quality checks, and system integration +--- + +# Chapter Outline + +## Purpose + +Create a comprehensive chapter outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing chapter outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the chapter outline +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the chapter outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Chapter Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-analytics-report/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-analytics-report/SKILL.md new file mode 100644 index 0000000..9b3d2bd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-analytics-report/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a content analytics report with structured process, quality checks, and system integration +--- + +# Content Analytics Report + +## Purpose + +Analyze and produce a comprehensive content analytics report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content analytics report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content analytics report +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content analytics report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Analytics Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-distribution/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-distribution/SKILL.md new file mode 100644 index 0000000..d097bd4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-distribution/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content distribution with structured process, quality checks, and system integration +--- + +# Content Distribution + +## Purpose + +Create a comprehensive content distribution that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content distribution documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content distribution +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content distribution using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Distribution + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-licensing/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-licensing/SKILL.md new file mode 100644 index 0000000..c90945e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-licensing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content licensing with structured process, quality checks, and system integration +--- + +# Content Licensing + +## Purpose + +Create a comprehensive content licensing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content licensing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content licensing +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content licensing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Licensing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-performance/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-performance/SKILL.md new file mode 100644 index 0000000..70a9572 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-performance/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content performance with structured process, quality checks, and system integration +--- + +# Content Performance + +## Purpose + +Create a comprehensive content performance that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content performance documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content performance +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content performance using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Performance + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-strategy-media/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-strategy-media/SKILL.md new file mode 100644 index 0000000..6b3049e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-strategy-media/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a content strategy media with structured process, quality checks, and system integration +--- + +# Content Strategy Media + +## Purpose + +Design and document a comprehensive content strategy media that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content strategy media documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content strategy media +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content strategy media using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Strategy Media + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/content-syndication/SKILL.md b/clowdex-download/.claude/.claude/skills/media/content-syndication/SKILL.md new file mode 100644 index 0000000..848bb50 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/content-syndication/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content syndication with structured process, quality checks, and system integration +--- + +# Content Syndication + +## Purpose + +Create a comprehensive content syndication that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content syndication documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content syndication +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content syndication using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Content Syndication + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/contributor-guidelines/SKILL.md b/clowdex-download/.claude/.claude/skills/media/contributor-guidelines/SKILL.md new file mode 100644 index 0000000..9f64c01 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/contributor-guidelines/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a contributor guidelines with structured process, quality checks, and system integration +--- + +# Contributor Guidelines + +## Purpose + +Design and document a comprehensive contributor guidelines that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing contributor guidelines documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the contributor guidelines +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the contributor guidelines using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Contributor Guidelines + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/correction-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/media/correction-policy/SKILL.md new file mode 100644 index 0000000..0f8d9f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/correction-policy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a correction policy with structured process, quality checks, and system integration +--- + +# Correction Policy + +## Purpose + +Create a comprehensive correction policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing correction policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the correction policy +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the correction policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Correction Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/cross-promotion/SKILL.md b/clowdex-download/.claude/.claude/skills/media/cross-promotion/SKILL.md new file mode 100644 index 0000000..09038f8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/cross-promotion/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cross promotion with structured process, quality checks, and system integration +--- + +# Cross Promotion + +## Purpose + +Create a comprehensive cross promotion that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross promotion documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross promotion +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross promotion using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Cross Promotion + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/editorial-calendar/SKILL.md b/clowdex-download/.claude/.claude/skills/media/editorial-calendar/SKILL.md new file mode 100644 index 0000000..a82ea17 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/editorial-calendar/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a editorial calendar with structured process, quality checks, and system integration +--- + +# Editorial Calendar + +## Purpose + +Design and document a comprehensive editorial calendar that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing editorial calendar documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the editorial calendar +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the editorial calendar using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Editorial Calendar + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/editorial-guidelines/SKILL.md b/clowdex-download/.claude/.claude/skills/media/editorial-guidelines/SKILL.md new file mode 100644 index 0000000..ef1edda --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/editorial-guidelines/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a editorial guidelines with structured process, quality checks, and system integration +--- + +# Editorial Guidelines + +## Purpose + +Design and document a comprehensive editorial guidelines that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing editorial guidelines documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the editorial guidelines +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the editorial guidelines using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Editorial Guidelines + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/editorial-style-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/media/editorial-style-guide/SKILL.md new file mode 100644 index 0000000..b78bacf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/editorial-style-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a editorial style guide with structured process, quality checks, and system integration +--- + +# Editorial Style Guide + +## Purpose + +Design and document a comprehensive editorial style guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing editorial style guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the editorial style guide +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the editorial style guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Editorial Style Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/fact-checking-process/SKILL.md b/clowdex-download/.claude/.claude/skills/media/fact-checking-process/SKILL.md new file mode 100644 index 0000000..744b1d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/fact-checking-process/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a fact checking process with structured process, quality checks, and system integration +--- + +# Fact Checking Process + +## Purpose + +Analyze and produce a comprehensive fact checking process that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fact checking process documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fact checking process +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fact checking process using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Fact Checking Process + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/feature-article/SKILL.md b/clowdex-download/.claude/.claude/skills/media/feature-article/SKILL.md new file mode 100644 index 0000000..54a6608 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/feature-article/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a feature article with structured process, quality checks, and system integration +--- + +# Feature Article + +## Purpose + +Create a comprehensive feature article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature article +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Feature Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/freelancer-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/media/freelancer-brief/SKILL.md new file mode 100644 index 0000000..ac05584 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/freelancer-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a freelancer brief with structured process, quality checks, and system integration +--- + +# Freelancer Brief + +## Purpose + +Create a comprehensive freelancer brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing freelancer brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the freelancer brief +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the freelancer brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Freelancer Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/interview-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/media/interview-prep/SKILL.md new file mode 100644 index 0000000..c36d8c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/interview-prep/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a interview prep with structured process, quality checks, and system integration +--- + +# Interview Prep + +## Purpose + +Create a comprehensive interview prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interview prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interview prep +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interview prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Interview Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/interview-questions/SKILL.md b/clowdex-download/.claude/.claude/skills/media/interview-questions/SKILL.md new file mode 100644 index 0000000..bf53ece --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/interview-questions/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a interview questions with structured process, quality checks, and system integration +--- + +# Interview Questions + +## Purpose + +Create a comprehensive interview questions that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interview questions documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interview questions +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interview questions using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Interview Questions + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/interview-transcript/SKILL.md b/clowdex-download/.claude/.claude/skills/media/interview-transcript/SKILL.md new file mode 100644 index 0000000..01958cd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/interview-transcript/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a interview transcript with structured process, quality checks, and system integration +--- + +# Interview Transcript + +## Purpose + +Create a comprehensive interview transcript that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing interview transcript documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the interview transcript +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the interview transcript using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Interview Transcript + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/investigative-piece/SKILL.md b/clowdex-download/.claude/.claude/skills/media/investigative-piece/SKILL.md new file mode 100644 index 0000000..e5da930 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/investigative-piece/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a investigative piece with structured process, quality checks, and system integration +--- + +# Investigative Piece + +## Purpose + +Create a comprehensive investigative piece that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investigative piece documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investigative piece +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investigative piece using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Investigative Piece + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/live-blog/SKILL.md b/clowdex-download/.claude/.claude/skills/media/live-blog/SKILL.md new file mode 100644 index 0000000..870fce9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/live-blog/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a live blog with structured process, quality checks, and system integration +--- + +# Live Blog + +## Purpose + +Create a comprehensive live blog that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing live blog documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the live blog +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the live blog using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Live Blog + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/live-event-coverage/SKILL.md b/clowdex-download/.claude/.claude/skills/media/live-event-coverage/SKILL.md new file mode 100644 index 0000000..c2fe4d6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/live-event-coverage/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a live event coverage with structured process, quality checks, and system integration +--- + +# Live Event Coverage + +## Purpose + +Create a comprehensive live event coverage that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing live event coverage documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the live event coverage +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the live event coverage using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Live Event Coverage + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/media-kit-creator/SKILL.md b/clowdex-download/.claude/.claude/skills/media/media-kit-creator/SKILL.md new file mode 100644 index 0000000..21ab26c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/media-kit-creator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a media kit creator with structured process, quality checks, and system integration +--- + +# Media Kit Creator + +## Purpose + +Create a comprehensive media kit creator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing media kit creator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the media kit creator +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the media kit creator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Media Kit Creator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/newsletter-growth/SKILL.md b/clowdex-download/.claude/.claude/skills/media/newsletter-growth/SKILL.md new file mode 100644 index 0000000..45f31a2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/newsletter-growth/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a newsletter growth with structured process, quality checks, and system integration +--- + +# Newsletter Growth + +## Purpose + +Create a comprehensive newsletter growth that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter growth documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter growth +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter growth using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Newsletter Growth + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/newsletter-launch/SKILL.md b/clowdex-download/.claude/.claude/skills/media/newsletter-launch/SKILL.md new file mode 100644 index 0000000..9f6ffc3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/newsletter-launch/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a newsletter launch with structured process, quality checks, and system integration +--- + +# Newsletter Launch + +## Purpose + +Create a comprehensive newsletter launch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter launch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter launch +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter launch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Newsletter Launch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/newsletter-monetization/SKILL.md b/clowdex-download/.claude/.claude/skills/media/newsletter-monetization/SKILL.md new file mode 100644 index 0000000..fd0a463 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/newsletter-monetization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a newsletter monetization with structured process, quality checks, and system integration +--- + +# Newsletter Monetization + +## Purpose + +Create a comprehensive newsletter monetization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing newsletter monetization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the newsletter monetization +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the newsletter monetization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Newsletter Monetization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/paywall-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/media/paywall-strategy/SKILL.md new file mode 100644 index 0000000..5d9968a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/paywall-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a paywall strategy with structured process, quality checks, and system integration +--- + +# Paywall Strategy + +## Purpose + +Design and document a comprehensive paywall strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing paywall strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the paywall strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the paywall strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Paywall Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/podcast-format-design/SKILL.md b/clowdex-download/.claude/.claude/skills/media/podcast-format-design/SKILL.md new file mode 100644 index 0000000..0e722d4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/podcast-format-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a podcast format design with structured process, quality checks, and system integration +--- + +# Podcast Format Design + +## Purpose + +Create a comprehensive podcast format design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast format design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast format design +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast format design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Podcast Format Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/podcast-launch-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/media/podcast-launch-plan/SKILL.md new file mode 100644 index 0000000..128d5df --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/podcast-launch-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a podcast launch plan with structured process, quality checks, and system integration +--- + +# Podcast Launch Plan + +## Purpose + +Design and document a comprehensive podcast launch plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast launch plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast launch plan +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast launch plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Podcast Launch Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/podcast-monetization/SKILL.md b/clowdex-download/.claude/.claude/skills/media/podcast-monetization/SKILL.md new file mode 100644 index 0000000..9df70e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/podcast-monetization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a podcast monetization with structured process, quality checks, and system integration +--- + +# Podcast Monetization + +## Purpose + +Create a comprehensive podcast monetization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast monetization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast monetization +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast monetization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Podcast Monetization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/republishing-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/media/republishing-strategy/SKILL.md new file mode 100644 index 0000000..1caadfe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/republishing-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a republishing strategy with structured process, quality checks, and system integration +--- + +# Republishing Strategy + +## Purpose + +Design and document a comprehensive republishing strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing republishing strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the republishing strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the republishing strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Republishing Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/social-media-promotion/SKILL.md b/clowdex-download/.claude/.claude/skills/media/social-media-promotion/SKILL.md new file mode 100644 index 0000000..82b7eca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/social-media-promotion/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a social media promotion with structured process, quality checks, and system integration +--- + +# Social Media Promotion + +## Purpose + +Create a comprehensive social media promotion that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media promotion documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media promotion +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media promotion using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Social Media Promotion + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/sponsorship-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/media/sponsorship-deck/SKILL.md new file mode 100644 index 0000000..da0c91c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/sponsorship-deck/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a sponsorship deck with structured process, quality checks, and system integration +--- + +# Sponsorship Deck + +## Purpose + +Create a comprehensive sponsorship deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sponsorship deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sponsorship deck +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sponsorship deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Sponsorship Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/submission-review/SKILL.md b/clowdex-download/.claude/.claude/skills/media/submission-review/SKILL.md new file mode 100644 index 0000000..aa412c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/submission-review/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a submission review with structured process, quality checks, and system integration +--- + +# Submission Review + +## Purpose + +Analyze and produce a comprehensive submission review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing submission review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the submission review +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the submission review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Submission Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/subscriber-acquisition/SKILL.md b/clowdex-download/.claude/.claude/skills/media/subscriber-acquisition/SKILL.md new file mode 100644 index 0000000..83c2b60 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/subscriber-acquisition/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a subscriber acquisition with structured process, quality checks, and system integration +--- + +# Subscriber Acquisition + +## Purpose + +Create a comprehensive subscriber acquisition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing subscriber acquisition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the subscriber acquisition +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the subscriber acquisition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Subscriber Acquisition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/video-editing-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/media/video-editing-brief/SKILL.md new file mode 100644 index 0000000..13330f1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/video-editing-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a video editing brief with structured process, quality checks, and system integration +--- + +# Video Editing Brief + +## Purpose + +Create a comprehensive video editing brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing video editing brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the video editing brief +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the video editing brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Video Editing Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/video-production-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/media/video-production-brief/SKILL.md new file mode 100644 index 0000000..09c468a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/video-production-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a video production brief with structured process, quality checks, and system integration +--- + +# Video Production Brief + +## Purpose + +Create a comprehensive video production brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing video production brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the video production brief +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the video production brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Video Production Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/media/youtube-channel-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/media/youtube-channel-plan/SKILL.md new file mode 100644 index 0000000..98ab6fb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/media/youtube-channel-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a youtube channel plan with structured process, quality checks, and system integration +--- + +# Youtube Channel Plan + +## Purpose + +Design and document a comprehensive youtube channel plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Media & Publishing + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube channel plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Editorial Calendar, Content Flywheel, PESO Model (Paid, Earned, Shared, Owned) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube channel plan +- Identify gaps, opportunities, and risks +- Define success metrics: Unique Visitors, Page Views, Time on Site, Subscriber Growth +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube channel plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Publish consistently — frequency beats quality for growth + +## Output Format + +```markdown +# Youtube Channel Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Editorial Calendar +- Content Flywheel +- PESO Model (Paid, Earned, Shared, Owned) +- Audience Development Funnel +- Monetization Ladder + +## Key Metrics +- Unique Visitors +- Page Views +- Time on Site +- Subscriber Growth +- Revenue Per User +- Content Velocity +- Engagement Rate + +## Best Practices +- Publish consistently — frequency beats quality for growth +- Headline is 80% of the battle +- Build email list from day one +- Diversify revenue (ads + subscriptions + events + products) +- Fact-check everything before publishing + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/990-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/990-prep/SKILL.md new file mode 100644 index 0000000..b318451 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/990-prep/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a 990 prep with structured process, quality checks, and system integration +--- + +# 990 Prep + +## Purpose + +Create a comprehensive 990 prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing 990 prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the 990 prep +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the 990 prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# 990 Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/advocacy-campaign/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/advocacy-campaign/SKILL.md new file mode 100644 index 0000000..417143c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/advocacy-campaign/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a advocacy campaign with structured process, quality checks, and system integration +--- + +# Advocacy Campaign + +## Purpose + +Design and document a comprehensive advocacy campaign that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing advocacy campaign documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the advocacy campaign +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the advocacy campaign using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Advocacy Campaign + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/annual-appeal/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/annual-appeal/SKILL.md new file mode 100644 index 0000000..6a3e4e2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/annual-appeal/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a annual appeal with structured process, quality checks, and system integration +--- + +# Annual Appeal + +## Purpose + +Create a comprehensive annual appeal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing annual appeal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the annual appeal +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the annual appeal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Annual Appeal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/annual-report-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/annual-report-nonprofit/SKILL.md new file mode 100644 index 0000000..fa43e22 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/annual-report-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a annual report nonprofit with structured process, quality checks, and system integration +--- + +# Annual Report Nonprofit + +## Purpose + +Analyze and produce a comprehensive annual report nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing annual report nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the annual report nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the annual report nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Annual Report Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/auction-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/auction-planning/SKILL.md new file mode 100644 index 0000000..11d9416 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/auction-planning/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a auction planning with structured process, quality checks, and system integration +--- + +# Auction Planning + +## Purpose + +Design and document a comprehensive auction planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing auction planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the auction planning +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the auction planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Auction Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/audit-prep-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/audit-prep-nonprofit/SKILL.md new file mode 100644 index 0000000..7cb12ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/audit-prep-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a audit prep nonprofit with structured process, quality checks, and system integration +--- + +# Audit Prep Nonprofit + +## Purpose + +Analyze and produce a comprehensive audit prep nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing audit prep nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the audit prep nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the audit prep nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Audit Prep Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/board-meeting-agenda/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/board-meeting-agenda/SKILL.md new file mode 100644 index 0000000..9d1dc24 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/board-meeting-agenda/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a board meeting agenda with structured process, quality checks, and system integration +--- + +# Board Meeting Agenda + +## Purpose + +Create a comprehensive board meeting agenda that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board meeting agenda documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board meeting agenda +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board meeting agenda using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Board Meeting Agenda + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/board-orientation/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/board-orientation/SKILL.md new file mode 100644 index 0000000..7bde210 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/board-orientation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a board orientation with structured process, quality checks, and system integration +--- + +# Board Orientation + +## Purpose + +Create a comprehensive board orientation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board orientation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board orientation +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board orientation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Board Orientation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/board-recruitment/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/board-recruitment/SKILL.md new file mode 100644 index 0000000..3e3cd25 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/board-recruitment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a board recruitment with structured process, quality checks, and system integration +--- + +# Board Recruitment + +## Purpose + +Create a comprehensive board recruitment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board recruitment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board recruitment +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board recruitment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Board Recruitment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/case-for-support/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/case-for-support/SKILL.md new file mode 100644 index 0000000..0a740cc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/case-for-support/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a case for support with structured process, quality checks, and system integration +--- + +# Case For Support + +## Purpose + +Create a comprehensive case for support that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing case for support documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the case for support +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the case for support using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Case For Support + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/cause-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/cause-marketing/SKILL.md new file mode 100644 index 0000000..299db59 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/cause-marketing/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a cause marketing with structured process, quality checks, and system integration +--- + +# Cause Marketing + +## Purpose + +Create a comprehensive cause marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cause marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cause marketing +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cause marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Cause Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/compliance-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/compliance-nonprofit/SKILL.md new file mode 100644 index 0000000..68f3049 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/compliance-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a compliance nonprofit with structured process, quality checks, and system integration +--- + +# Compliance Nonprofit + +## Purpose + +Create a comprehensive compliance nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing compliance nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the compliance nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the compliance nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Compliance Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/conflict-of-interest/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/conflict-of-interest/SKILL.md new file mode 100644 index 0000000..3fb7784 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/conflict-of-interest/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a conflict of interest with structured process, quality checks, and system integration +--- + +# Conflict Of Interest + +## Purpose + +Create a comprehensive conflict of interest that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conflict of interest documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conflict of interest +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conflict of interest using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Conflict Of Interest + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/corporate-partnership/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/corporate-partnership/SKILL.md new file mode 100644 index 0000000..0f31eb8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/corporate-partnership/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a corporate partnership with structured process, quality checks, and system integration +--- + +# Corporate Partnership + +## Purpose + +Create a comprehensive corporate partnership that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate partnership documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate partnership +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate partnership using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Corporate Partnership + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/corporate-sponsorship/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/corporate-sponsorship/SKILL.md new file mode 100644 index 0000000..36f3db2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/corporate-sponsorship/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a corporate sponsorship with structured process, quality checks, and system integration +--- + +# Corporate Sponsorship + +## Purpose + +Create a comprehensive corporate sponsorship that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate sponsorship documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate sponsorship +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate sponsorship using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Corporate Sponsorship + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/crowdfunding-campaign/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/crowdfunding-campaign/SKILL.md new file mode 100644 index 0000000..79b0468 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/crowdfunding-campaign/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a crowdfunding campaign with structured process, quality checks, and system integration +--- + +# Crowdfunding Campaign + +## Purpose + +Design and document a comprehensive crowdfunding campaign that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crowdfunding campaign documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crowdfunding campaign +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crowdfunding campaign using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Crowdfunding Campaign + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/donation-thank-you/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/donation-thank-you/SKILL.md new file mode 100644 index 0000000..a731674 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/donation-thank-you/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a donation thank you with structured process, quality checks, and system integration +--- + +# Donation Thank You + +## Purpose + +Create a comprehensive donation thank you that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing donation thank you documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the donation thank you +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the donation thank you using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Donation Thank You + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/donor-cultivation/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/donor-cultivation/SKILL.md new file mode 100644 index 0000000..07fccae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/donor-cultivation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a donor cultivation with structured process, quality checks, and system integration +--- + +# Donor Cultivation + +## Purpose + +Create a comprehensive donor cultivation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing donor cultivation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the donor cultivation +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the donor cultivation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Donor Cultivation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/donor-retention/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/donor-retention/SKILL.md new file mode 100644 index 0000000..cf4e75c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/donor-retention/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a donor retention with structured process, quality checks, and system integration +--- + +# Donor Retention + +## Purpose + +Create a comprehensive donor retention that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing donor retention documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the donor retention +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the donor retention using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Donor Retention + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/donor-segmentation/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/donor-segmentation/SKILL.md new file mode 100644 index 0000000..33cddad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/donor-segmentation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a donor segmentation with structured process, quality checks, and system integration +--- + +# Donor Segmentation + +## Purpose + +Create a comprehensive donor segmentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing donor segmentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the donor segmentation +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the donor segmentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Donor Segmentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/event-fundraiser/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/event-fundraiser/SKILL.md new file mode 100644 index 0000000..32c296d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/event-fundraiser/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a event fundraiser with structured process, quality checks, and system integration +--- + +# Event Fundraiser + +## Purpose + +Create a comprehensive event fundraiser that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event fundraiser documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event fundraiser +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event fundraiser using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Event Fundraiser + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/financial-report-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/financial-report-nonprofit/SKILL.md new file mode 100644 index 0000000..c534e21 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/financial-report-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a financial report nonprofit with structured process, quality checks, and system integration +--- + +# Financial Report Nonprofit + +## Purpose + +Analyze and produce a comprehensive financial report nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing financial report nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the financial report nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the financial report nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Financial Report Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-email/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-email/SKILL.md new file mode 100644 index 0000000..92a16dd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-email/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a fundraising email with structured process, quality checks, and system integration +--- + +# Fundraising Email + +## Purpose + +Create a comprehensive fundraising email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fundraising email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fundraising email +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fundraising email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Fundraising Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-plan/SKILL.md new file mode 100644 index 0000000..d427bb2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/fundraising-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a fundraising plan with structured process, quality checks, and system integration +--- + +# Fundraising Plan + +## Purpose + +Design and document a comprehensive fundraising plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fundraising plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fundraising plan +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fundraising plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Fundraising Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/gala-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/gala-planning/SKILL.md new file mode 100644 index 0000000..fbadef2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/gala-planning/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a gala planning with structured process, quality checks, and system integration +--- + +# Gala Planning + +## Purpose + +Design and document a comprehensive gala planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gala planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gala planning +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gala planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Gala Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/gift-acceptance-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/gift-acceptance-policy/SKILL.md new file mode 100644 index 0000000..a2bb4e0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/gift-acceptance-policy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a gift acceptance policy with structured process, quality checks, and system integration +--- + +# Gift Acceptance Policy + +## Purpose + +Create a comprehensive gift acceptance policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gift acceptance policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gift acceptance policy +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gift acceptance policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Gift Acceptance Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/giving-tuesday/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/giving-tuesday/SKILL.md new file mode 100644 index 0000000..174a00c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/giving-tuesday/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a giving tuesday with structured process, quality checks, and system integration +--- + +# Giving Tuesday + +## Purpose + +Create a comprehensive giving tuesday that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing giving tuesday documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the giving tuesday +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the giving tuesday using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Giving Tuesday + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/grant-budget/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/grant-budget/SKILL.md new file mode 100644 index 0000000..06fc40e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/grant-budget/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a grant budget with structured process, quality checks, and system integration +--- + +# Grant Budget + +## Purpose + +Create a comprehensive grant budget that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grant budget documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grant budget +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grant budget using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Grant Budget + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/grant-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/grant-proposal/SKILL.md new file mode 100644 index 0000000..951454b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/grant-proposal/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a grant proposal with structured process, quality checks, and system integration +--- + +# Grant Proposal + +## Purpose + +Create a comprehensive grant proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grant proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grant proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grant proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Grant Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/grant-research/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/grant-research/SKILL.md new file mode 100644 index 0000000..8adad5e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/grant-research/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a grant research with structured process, quality checks, and system integration +--- + +# Grant Research + +## Purpose + +Create a comprehensive grant research that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grant research documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grant research +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grant research using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Grant Research + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/grassroots-mobilization/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/grassroots-mobilization/SKILL.md new file mode 100644 index 0000000..4aeded3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/grassroots-mobilization/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a grassroots mobilization with structured process, quality checks, and system integration +--- + +# Grassroots Mobilization + +## Purpose + +Create a comprehensive grassroots mobilization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing grassroots mobilization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the grassroots mobilization +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the grassroots mobilization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Grassroots Mobilization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/impact-report/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/impact-report/SKILL.md new file mode 100644 index 0000000..67969ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/impact-report/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a impact report with structured process, quality checks, and system integration +--- + +# Impact Report + +## Purpose + +Analyze and produce a comprehensive impact report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing impact report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the impact report +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the impact report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Impact Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/lapsed-donor-reactivation/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/lapsed-donor-reactivation/SKILL.md new file mode 100644 index 0000000..2f8892f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/lapsed-donor-reactivation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a lapsed donor reactivation with structured process, quality checks, and system integration +--- + +# Lapsed Donor Reactivation + +## Purpose + +Create a comprehensive lapsed donor reactivation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lapsed donor reactivation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lapsed donor reactivation +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lapsed donor reactivation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Lapsed Donor Reactivation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/logic-model/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/logic-model/SKILL.md new file mode 100644 index 0000000..c3d0c37 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/logic-model/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a logic model with structured process, quality checks, and system integration +--- + +# Logic Model + +## Purpose + +Design and document a comprehensive logic model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing logic model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the logic model +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the logic model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Logic Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/major-gift-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/major-gift-strategy/SKILL.md new file mode 100644 index 0000000..5b87969 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/major-gift-strategy/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a major gift strategy with structured process, quality checks, and system integration +--- + +# Major Gift Strategy + +## Purpose + +Design and document a comprehensive major gift strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing major gift strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the major gift strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the major gift strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Major Gift Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/needs-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/needs-assessment/SKILL.md new file mode 100644 index 0000000..cedd495 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/needs-assessment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a needs assessment with structured process, quality checks, and system integration +--- + +# Needs Assessment + +## Purpose + +Analyze and produce a comprehensive needs assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing needs assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the needs assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the needs assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Needs Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/nonprofit-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/nonprofit-marketing-plan/SKILL.md new file mode 100644 index 0000000..9ada216 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/nonprofit-marketing-plan/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a nonprofit marketing plan with structured process, quality checks, and system integration +--- + +# Nonprofit Marketing Plan + +## Purpose + +Design and document a comprehensive nonprofit marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing nonprofit marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the nonprofit marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the nonprofit marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Nonprofit Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/outcomes-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/outcomes-framework/SKILL.md new file mode 100644 index 0000000..e33190e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/outcomes-framework/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a outcomes framework with structured process, quality checks, and system integration +--- + +# Outcomes Framework + +## Purpose + +Design and document a comprehensive outcomes framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing outcomes framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the outcomes framework +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the outcomes framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Outcomes Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/peer-to-peer-fundraising/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/peer-to-peer-fundraising/SKILL.md new file mode 100644 index 0000000..b23f875 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/peer-to-peer-fundraising/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a peer to peer fundraising with structured process, quality checks, and system integration +--- + +# Peer To Peer Fundraising + +## Purpose + +Create a comprehensive peer to peer fundraising that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing peer to peer fundraising documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the peer to peer fundraising +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the peer to peer fundraising using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Peer To Peer Fundraising + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/policy-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/policy-brief/SKILL.md new file mode 100644 index 0000000..5e99237 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/policy-brief/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a policy brief with structured process, quality checks, and system integration +--- + +# Policy Brief + +## Purpose + +Create a comprehensive policy brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing policy brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the policy brief +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the policy brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Policy Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/program-design/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/program-design/SKILL.md new file mode 100644 index 0000000..daabd10 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/program-design/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a program design with structured process, quality checks, and system integration +--- + +# Program Design + +## Purpose + +Create a comprehensive program design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing program design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the program design +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the program design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Program Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/program-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/program-evaluation/SKILL.md new file mode 100644 index 0000000..2501b9f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/program-evaluation/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Analyze and produce a program evaluation with structured process, quality checks, and system integration +--- + +# Program Evaluation + +## Purpose + +Analyze and produce a comprehensive program evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing program evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the program evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the program evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Program Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/storytelling-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/storytelling-nonprofit/SKILL.md new file mode 100644 index 0000000..71d94ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/storytelling-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a storytelling nonprofit with structured process, quality checks, and system integration +--- + +# Storytelling Nonprofit + +## Purpose + +Create a comprehensive storytelling nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing storytelling nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the storytelling nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the storytelling nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Storytelling Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/strategic-plan-nonprofit/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/strategic-plan-nonprofit/SKILL.md new file mode 100644 index 0000000..1f306c0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/strategic-plan-nonprofit/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Design and document a strategic plan nonprofit with structured process, quality checks, and system integration +--- + +# Strategic Plan Nonprofit + +## Purpose + +Design and document a comprehensive strategic plan nonprofit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing strategic plan nonprofit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the strategic plan nonprofit +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the strategic plan nonprofit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Strategic Plan Nonprofit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/theory-of-change/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/theory-of-change/SKILL.md new file mode 100644 index 0000000..31e4626 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/theory-of-change/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a theory of change with structured process, quality checks, and system integration +--- + +# Theory Of Change + +## Purpose + +Create a comprehensive theory of change that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing theory of change documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the theory of change +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the theory of change using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Theory Of Change + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-onboarding/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-onboarding/SKILL.md new file mode 100644 index 0000000..88ee4f5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-onboarding/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a volunteer onboarding with structured process, quality checks, and system integration +--- + +# Volunteer Onboarding + +## Purpose + +Create a comprehensive volunteer onboarding that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing volunteer onboarding documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the volunteer onboarding +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the volunteer onboarding using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Volunteer Onboarding + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recognition/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recognition/SKILL.md new file mode 100644 index 0000000..343f440 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recognition/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a volunteer recognition with structured process, quality checks, and system integration +--- + +# Volunteer Recognition + +## Purpose + +Create a comprehensive volunteer recognition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing volunteer recognition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the volunteer recognition +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the volunteer recognition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Volunteer Recognition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recruitment/SKILL.md b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recruitment/SKILL.md new file mode 100644 index 0000000..c74ca63 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/nonprofit/volunteer-recruitment/SKILL.md @@ -0,0 +1,131 @@ +--- +description: Create a volunteer recruitment with structured process, quality checks, and system integration +--- + +# Volunteer Recruitment + +## Purpose + +Create a comprehensive volunteer recruitment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Nonprofit & Social Impact + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing volunteer recruitment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Theory of Change, Logic Model, Fundraising Pyramid + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the volunteer recruitment +- Identify gaps, opportunities, and risks +- Define success metrics: Donor Retention Rate, Cost Per Dollar Raised, Program Efficiency Ratio, Impact per Dollar +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the volunteer recruitment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Thank donors within 48 hours + +## Output Format + +```markdown +# Volunteer Recruitment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Theory of Change +- Logic Model +- Fundraising Pyramid +- Donor Lifecycle +- Impact Measurement Framework + +## Key Metrics +- Donor Retention Rate +- Cost Per Dollar Raised +- Program Efficiency Ratio +- Impact per Dollar +- Volunteer Retention Rate +- Grant Success Rate + +## Best Practices +- Thank donors within 48 hours +- Report impact, not just activities +- Diversify funding sources (no single source > 30%) +- Board members should give or get +- Overhead ratio is not a measure of effectiveness + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/action-item-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/action-item-tracker/SKILL.md new file mode 100644 index 0000000..453582e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/action-item-tracker/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a action item tracker with structured process, quality checks, and system integration +--- + +# Action Item Tracker + +## Purpose + +Analyze and produce a comprehensive action item tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing action item tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the action item tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the action item tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Action Item Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/automation-opportunity-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/automation-opportunity-audit/SKILL.md new file mode 100644 index 0000000..8e69511 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/automation-opportunity-audit/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a automation opportunity audit with structured process, quality checks, and system integration +--- + +# Automation Opportunity Audit + +## Purpose + +Analyze and produce a comprehensive automation opportunity audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing automation opportunity audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the automation opportunity audit +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the automation opportunity audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Automation Opportunity Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/bottleneck-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/bottleneck-analysis/SKILL.md new file mode 100644 index 0000000..cf16d94 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/bottleneck-analysis/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a bottleneck analysis with structured process, quality checks, and system integration +--- + +# Bottleneck Analysis + +## Purpose + +Analyze and produce a comprehensive bottleneck analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bottleneck analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bottleneck analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bottleneck analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Bottleneck Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/business-continuity-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/business-continuity-plan/SKILL.md new file mode 100644 index 0000000..bfaf3d1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/business-continuity-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a business continuity plan with structured process, quality checks, and system integration +--- + +# Business Continuity Plan + +## Purpose + +Design and document a comprehensive business continuity plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business continuity plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business continuity plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business continuity plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Business Continuity Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/capacity-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/capacity-planning/SKILL.md new file mode 100644 index 0000000..be35200 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/capacity-planning/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a capacity planning with structured process, quality checks, and system integration +--- + +# Capacity Planning + +## Purpose + +Design and document a comprehensive capacity planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing capacity planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the capacity planning +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the capacity planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Capacity Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/change-management-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/change-management-plan/SKILL.md new file mode 100644 index 0000000..4a055ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/change-management-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a change management plan with structured process, quality checks, and system integration +--- + +# Change Management Plan + +## Purpose + +Design and document a comprehensive change management plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing change management plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the change management plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the change management plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Change Management Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/communication-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/communication-plan/SKILL.md new file mode 100644 index 0000000..2a09731 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/communication-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a communication plan with structured process, quality checks, and system integration +--- + +# Communication Plan + +## Purpose + +Design and document a comprehensive communication plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing communication plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the communication plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the communication plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Communication Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/contingency-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/contingency-plan/SKILL.md new file mode 100644 index 0000000..8e6250a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/contingency-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a contingency plan with structured process, quality checks, and system integration +--- + +# Contingency Plan + +## Purpose + +Design and document a comprehensive contingency plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing contingency plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the contingency plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the contingency plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Contingency Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/cross-functional-alignment/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/cross-functional-alignment/SKILL.md new file mode 100644 index 0000000..c8d2ad3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/cross-functional-alignment/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a cross functional alignment with structured process, quality checks, and system integration +--- + +# Cross Functional Alignment + +## Purpose + +Create a comprehensive cross functional alignment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross functional alignment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross functional alignment +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross functional alignment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Cross Functional Alignment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/decision-log/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/decision-log/SKILL.md new file mode 100644 index 0000000..903dbe4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/decision-log/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a decision log with structured process, quality checks, and system integration +--- + +# Decision Log + +## Purpose + +Create a comprehensive decision log that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing decision log documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the decision log +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the decision log using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Decision Log + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/defect-tracking/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/defect-tracking/SKILL.md new file mode 100644 index 0000000..e7e3872 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/defect-tracking/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a defect tracking with structured process, quality checks, and system integration +--- + +# Defect Tracking + +## Purpose + +Create a comprehensive defect tracking that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing defect tracking documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the defect tracking +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the defect tracking using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Defect Tracking + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/delegation-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/delegation-framework/SKILL.md new file mode 100644 index 0000000..9b118b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/delegation-framework/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a delegation framework with structured process, quality checks, and system integration +--- + +# Delegation Framework + +## Purpose + +Design and document a comprehensive delegation framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing delegation framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the delegation framework +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the delegation framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Delegation Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/disaster-recovery-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/disaster-recovery-plan/SKILL.md new file mode 100644 index 0000000..c166943 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/disaster-recovery-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a disaster recovery plan with structured process, quality checks, and system integration +--- + +# Disaster Recovery Plan + +## Purpose + +Design and document a comprehensive disaster recovery plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing disaster recovery plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the disaster recovery plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the disaster recovery plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Disaster Recovery Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/efficiency-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/efficiency-audit/SKILL.md new file mode 100644 index 0000000..429d440 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/efficiency-audit/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a efficiency audit with structured process, quality checks, and system integration +--- + +# Efficiency Audit + +## Purpose + +Analyze and produce a comprehensive efficiency audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing efficiency audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the efficiency audit +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the efficiency audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Efficiency Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/executive-summary/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/executive-summary/SKILL.md new file mode 100644 index 0000000..fdf555d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/executive-summary/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a executive summary with structured process, quality checks, and system integration +--- + +# Executive Summary + +## Purpose + +Create a comprehensive executive summary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive summary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive summary +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive summary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Executive Summary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/goal-setting-workshop/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/goal-setting-workshop/SKILL.md new file mode 100644 index 0000000..36414fc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/goal-setting-workshop/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a goal setting workshop with structured process, quality checks, and system integration +--- + +# Goal Setting Workshop + +## Purpose + +Create a comprehensive goal setting workshop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing goal setting workshop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the goal setting workshop +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the goal setting workshop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Goal Setting Workshop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/handover-document/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/handover-document/SKILL.md new file mode 100644 index 0000000..ca59538 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/handover-document/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a handover document with structured process, quality checks, and system integration +--- + +# Handover Document + +## Purpose + +Create a comprehensive handover document that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing handover document documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the handover document +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the handover document using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Handover Document + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/incident-management/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/incident-management/SKILL.md new file mode 100644 index 0000000..fadc08e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/incident-management/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a incident management with structured process, quality checks, and system integration +--- + +# Incident Management + +## Purpose + +Create a comprehensive incident management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incident management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incident management +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incident management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Incident Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/inventory-management/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/inventory-management/SKILL.md new file mode 100644 index 0000000..603e7bb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/inventory-management/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a inventory management with structured process, quality checks, and system integration +--- + +# Inventory Management + +## Purpose + +Create a comprehensive inventory management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inventory management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inventory management +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inventory management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Inventory Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/kanban-board-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/kanban-board-setup/SKILL.md new file mode 100644 index 0000000..c7a966e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/kanban-board-setup/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a kanban board setup with structured process, quality checks, and system integration +--- + +# Kanban Board Setup + +## Purpose + +Design and document a comprehensive kanban board setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kanban board setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kanban board setup +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kanban board setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Kanban Board Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/kpi-definition/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/kpi-definition/SKILL.md new file mode 100644 index 0000000..a48b9e8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/kpi-definition/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a kpi definition with structured process, quality checks, and system integration +--- + +# Kpi Definition + +## Purpose + +Create a comprehensive kpi definition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kpi definition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kpi definition +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kpi definition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Kpi Definition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/lean-six-sigma/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/lean-six-sigma/SKILL.md new file mode 100644 index 0000000..90f8bfc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/lean-six-sigma/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a lean six sigma with structured process, quality checks, and system integration +--- + +# Lean Six Sigma + +## Purpose + +Create a comprehensive lean six sigma that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lean six sigma documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lean six sigma +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lean six sigma using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Lean Six Sigma + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/lessons-learned/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/lessons-learned/SKILL.md new file mode 100644 index 0000000..107bb5a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/lessons-learned/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a lessons learned with structured process, quality checks, and system integration +--- + +# Lessons Learned + +## Purpose + +Create a comprehensive lessons learned that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lessons learned documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lessons learned +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lessons learned using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Lessons Learned + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/logistics-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/logistics-planning/SKILL.md new file mode 100644 index 0000000..afe6a10 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/logistics-planning/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a logistics planning with structured process, quality checks, and system integration +--- + +# Logistics Planning + +## Purpose + +Design and document a comprehensive logistics planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing logistics planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the logistics planning +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the logistics planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Logistics Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/meeting-agenda/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/meeting-agenda/SKILL.md new file mode 100644 index 0000000..4cb76b5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/meeting-agenda/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a meeting agenda with structured process, quality checks, and system integration +--- + +# Meeting Agenda + +## Purpose + +Create a comprehensive meeting agenda that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting agenda documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting agenda +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting agenda using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Meeting Agenda + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/meeting-notes/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/meeting-notes/SKILL.md new file mode 100644 index 0000000..5402917 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/meeting-notes/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a meeting notes with structured process, quality checks, and system integration +--- + +# Meeting Notes + +## Purpose + +Create a comprehensive meeting notes that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting notes documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting notes +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting notes using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Meeting Notes + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/offboarding-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/offboarding-checklist/SKILL.md new file mode 100644 index 0000000..8d449a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/offboarding-checklist/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a offboarding checklist with structured process, quality checks, and system integration +--- + +# Offboarding Checklist + +## Purpose + +Analyze and produce a comprehensive offboarding checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing offboarding checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the offboarding checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the offboarding checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Offboarding Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/okr-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/okr-framework/SKILL.md new file mode 100644 index 0000000..ee74784 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/okr-framework/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a okr framework with structured process, quality checks, and system integration +--- + +# Okr Framework + +## Purpose + +Design and document a comprehensive okr framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing okr framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the okr framework +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the okr framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Okr Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/onboarding-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/onboarding-checklist/SKILL.md new file mode 100644 index 0000000..bac71d9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/onboarding-checklist/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a onboarding checklist with structured process, quality checks, and system integration +--- + +# Onboarding Checklist + +## Purpose + +Analyze and produce a comprehensive onboarding checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Onboarding Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/operating-rhythm/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/operating-rhythm/SKILL.md new file mode 100644 index 0000000..12f2971 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/operating-rhythm/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a operating rhythm with structured process, quality checks, and system integration +--- + +# Operating Rhythm + +## Purpose + +Create a comprehensive operating rhythm that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing operating rhythm documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the operating rhythm +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the operating rhythm using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Operating Rhythm + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/post-mortem/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/post-mortem/SKILL.md new file mode 100644 index 0000000..d04f361 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/post-mortem/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a post mortem with structured process, quality checks, and system integration +--- + +# Post Mortem + +## Purpose + +Create a comprehensive post mortem that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing post mortem documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the post mortem +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the post mortem using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Post Mortem + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/process-map/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/process-map/SKILL.md new file mode 100644 index 0000000..a1209da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/process-map/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a process map with structured process, quality checks, and system integration +--- + +# Process Map + +## Purpose + +Create a comprehensive process map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing process map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the process map +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the process map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Process Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/process-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/process-optimization/SKILL.md new file mode 100644 index 0000000..688d553 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/process-optimization/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a process optimization with structured process, quality checks, and system integration +--- + +# Process Optimization + +## Purpose + +Create a comprehensive process optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing process optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the process optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the process optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Process Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/progress-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/progress-dashboard/SKILL.md new file mode 100644 index 0000000..04d6eff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/progress-dashboard/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a progress dashboard with structured process, quality checks, and system integration +--- + +# Progress Dashboard + +## Purpose + +Analyze and produce a comprehensive progress dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing progress dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the progress dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the progress dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Progress Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/project-charter/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/project-charter/SKILL.md new file mode 100644 index 0000000..a8508e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/project-charter/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a project charter with structured process, quality checks, and system integration +--- + +# Project Charter + +## Purpose + +Create a comprehensive project charter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project charter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project charter +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project charter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Project Charter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/project-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/project-plan/SKILL.md new file mode 100644 index 0000000..a77662d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/project-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a project plan with structured process, quality checks, and system integration +--- + +# Project Plan + +## Purpose + +Design and document a comprehensive project plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Project Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/project-timeline/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/project-timeline/SKILL.md new file mode 100644 index 0000000..1151b77 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/project-timeline/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a project timeline with structured process, quality checks, and system integration +--- + +# Project Timeline + +## Purpose + +Create a comprehensive project timeline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project timeline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project timeline +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project timeline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Project Timeline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/quality-assurance-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/quality-assurance-plan/SKILL.md new file mode 100644 index 0000000..a2081df --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/quality-assurance-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a quality assurance plan with structured process, quality checks, and system integration +--- + +# Quality Assurance Plan + +## Purpose + +Design and document a comprehensive quality assurance plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quality assurance plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quality assurance plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quality assurance plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Quality Assurance Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/quality-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/quality-checklist/SKILL.md new file mode 100644 index 0000000..47b2d3b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/quality-checklist/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a quality checklist with structured process, quality checks, and system integration +--- + +# Quality Checklist + +## Purpose + +Analyze and produce a comprehensive quality checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quality checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quality checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quality checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Quality Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/raci-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/raci-matrix/SKILL.md new file mode 100644 index 0000000..19cfe38 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/raci-matrix/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a raci matrix with structured process, quality checks, and system integration +--- + +# Raci Matrix + +## Purpose + +Create a comprehensive raci matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing raci matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the raci matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the raci matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Raci Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/resource-allocation/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/resource-allocation/SKILL.md new file mode 100644 index 0000000..df747b9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/resource-allocation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a resource allocation with structured process, quality checks, and system integration +--- + +# Resource Allocation + +## Purpose + +Create a comprehensive resource allocation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing resource allocation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the resource allocation +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the resource allocation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Resource Allocation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/responsibility-assignment/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/responsibility-assignment/SKILL.md new file mode 100644 index 0000000..48e2d10 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/responsibility-assignment/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a responsibility assignment with structured process, quality checks, and system integration +--- + +# Responsibility Assignment + +## Purpose + +Create a comprehensive responsibility assignment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing responsibility assignment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the responsibility assignment +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the responsibility assignment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Responsibility Assignment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/risk-mitigation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/risk-mitigation-plan/SKILL.md new file mode 100644 index 0000000..25a0c05 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/risk-mitigation-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a risk mitigation plan with structured process, quality checks, and system integration +--- + +# Risk Mitigation Plan + +## Purpose + +Design and document a comprehensive risk mitigation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing risk mitigation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the risk mitigation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the risk mitigation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Risk Mitigation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/risk-register/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/risk-register/SKILL.md new file mode 100644 index 0000000..b7d4018 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/risk-register/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a risk register with structured process, quality checks, and system integration +--- + +# Risk Register + +## Purpose + +Create a comprehensive risk register that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing risk register documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the risk register +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the risk register using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Risk Register + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/sop-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/sop-writer/SKILL.md new file mode 100644 index 0000000..dad3a8c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/sop-writer/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a sop writer with structured process, quality checks, and system integration +--- + +# Sop Writer + +## Purpose + +Create a comprehensive sop writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sop writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sop writer +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sop writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Sop Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/sprint-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/sprint-planning/SKILL.md new file mode 100644 index 0000000..3ede227 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/sprint-planning/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a sprint planning with structured process, quality checks, and system integration +--- + +# Sprint Planning + +## Purpose + +Design and document a comprehensive sprint planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sprint planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sprint planning +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sprint planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Sprint Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/sprint-retrospective/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/sprint-retrospective/SKILL.md new file mode 100644 index 0000000..e51bc18 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/sprint-retrospective/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a sprint retrospective with structured process, quality checks, and system integration +--- + +# Sprint Retrospective + +## Purpose + +Create a comprehensive sprint retrospective that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sprint retrospective documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sprint retrospective +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sprint retrospective using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Sprint Retrospective + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/sprint-review/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/sprint-review/SKILL.md new file mode 100644 index 0000000..1db281e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/sprint-review/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a sprint review with structured process, quality checks, and system integration +--- + +# Sprint Review + +## Purpose + +Analyze and produce a comprehensive sprint review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sprint review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sprint review +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sprint review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Sprint Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/stakeholder-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/stakeholder-analysis/SKILL.md new file mode 100644 index 0000000..a612c1b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/stakeholder-analysis/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a stakeholder analysis with structured process, quality checks, and system integration +--- + +# Stakeholder Analysis + +## Purpose + +Analyze and produce a comprehensive stakeholder analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stakeholder analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stakeholder analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stakeholder analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Stakeholder Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/status-report/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/status-report/SKILL.md new file mode 100644 index 0000000..b2fc900 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/status-report/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a status report with structured process, quality checks, and system integration +--- + +# Status Report + +## Purpose + +Analyze and produce a comprehensive status report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing status report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the status report +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the status report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Status Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/supply-chain-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/supply-chain-optimization/SKILL.md new file mode 100644 index 0000000..2d75b97 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/supply-chain-optimization/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a supply chain optimization with structured process, quality checks, and system integration +--- + +# Supply Chain Optimization + +## Purpose + +Create a comprehensive supply chain optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing supply chain optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the supply chain optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the supply chain optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Supply Chain Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/team-charter/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/team-charter/SKILL.md new file mode 100644 index 0000000..3bf9ac2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/team-charter/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a team charter with structured process, quality checks, and system integration +--- + +# Team Charter + +## Purpose + +Create a comprehensive team charter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing team charter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the team charter +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the team charter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Team Charter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/tech-stack-review/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/tech-stack-review/SKILL.md new file mode 100644 index 0000000..0b2dc9a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/tech-stack-review/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a tech stack review with structured process, quality checks, and system integration +--- + +# Tech Stack Review + +## Purpose + +Analyze and produce a comprehensive tech stack review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tech stack review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tech stack review +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tech stack review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Tech Stack Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/time-tracking-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/time-tracking-analysis/SKILL.md new file mode 100644 index 0000000..05750dd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/time-tracking-analysis/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a time tracking analysis with structured process, quality checks, and system integration +--- + +# Time Tracking Analysis + +## Purpose + +Analyze and produce a comprehensive time tracking analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing time tracking analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the time tracking analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the time tracking analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Time Tracking Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/tool-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/tool-evaluation/SKILL.md new file mode 100644 index 0000000..ef81dd7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/tool-evaluation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a tool evaluation with structured process, quality checks, and system integration +--- + +# Tool Evaluation + +## Purpose + +Analyze and produce a comprehensive tool evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tool evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tool evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tool evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Tool Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/vendor-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/vendor-evaluation/SKILL.md new file mode 100644 index 0000000..d4db15b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/vendor-evaluation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a vendor evaluation with structured process, quality checks, and system integration +--- + +# Vendor Evaluation + +## Purpose + +Analyze and produce a comprehensive vendor evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Vendor Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/vendor-onboarding/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/vendor-onboarding/SKILL.md new file mode 100644 index 0000000..f73bcea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/vendor-onboarding/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a vendor onboarding with structured process, quality checks, and system integration +--- + +# Vendor Onboarding + +## Purpose + +Create a comprehensive vendor onboarding that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor onboarding documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor onboarding +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor onboarding using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Vendor Onboarding + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/vendor-scorecard/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/vendor-scorecard/SKILL.md new file mode 100644 index 0000000..a8b32cb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/vendor-scorecard/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a vendor scorecard with structured process, quality checks, and system integration +--- + +# Vendor Scorecard + +## Purpose + +Analyze and produce a comprehensive vendor scorecard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor scorecard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor scorecard +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor scorecard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Vendor Scorecard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/workflow-design/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/workflow-design/SKILL.md new file mode 100644 index 0000000..67aeb5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/workflow-design/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a workflow design with structured process, quality checks, and system integration +--- + +# Workflow Design + +## Purpose + +Create a comprehensive workflow design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workflow design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workflow design +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workflow design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Workflow Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/operations/workload-balancing/SKILL.md b/clowdex-download/.claude/.claude/skills/operations/workload-balancing/SKILL.md new file mode 100644 index 0000000..5cbf1ae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/operations/workload-balancing/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a workload balancing with structured process, quality checks, and system integration +--- + +# Workload Balancing + +## Purpose + +Create a comprehensive workload balancing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Operations & Project Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing workload balancing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean, Six Sigma (DMAIC), Agile/Scrum + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the workload balancing +- Identify gaps, opportunities, and risks +- Define success metrics: Cycle Time, Throughput, Utilization Rate, Error Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the workload balancing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Document the process before optimizing it + +## Output Format + +```markdown +# Workload Balancing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean +- Six Sigma (DMAIC) +- Agile/Scrum +- Kanban +- OKRs +- RACI Matrix +- Theory of Constraints +- Kaizen + +## Key Metrics +- Cycle Time +- Throughput +- Utilization Rate +- Error Rate +- On-Time Delivery +- Process Compliance +- Cost Per Unit + +## Best Practices +- Document the process before optimizing it +- Measure baseline before making changes +- Automate repeatable tasks (ROI > 3 months) +- Review SOPs quarterly +- Single owner for every process + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/ab-test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/ab-test-plan/SKILL.md new file mode 100644 index 0000000..126eb4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/ab-test-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a ab test plan with structured process, quality checks, and system integration +--- + +# Ab Test Plan + +## Purpose + +Design and document a comprehensive ab test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ab test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ab test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ab test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Ab Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/acceptance-criteria/SKILL.md b/clowdex-download/.claude/.claude/skills/product/acceptance-criteria/SKILL.md new file mode 100644 index 0000000..f850d15 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/acceptance-criteria/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a acceptance criteria with structured process, quality checks, and system integration +--- + +# Acceptance Criteria + +## Purpose + +Create a comprehensive acceptance criteria that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing acceptance criteria documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the acceptance criteria +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the acceptance criteria using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Acceptance Criteria + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/activation-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/product/activation-checklist/SKILL.md new file mode 100644 index 0000000..285993b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/activation-checklist/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a activation checklist with structured process, quality checks, and system integration +--- + +# Activation Checklist + +## Purpose + +Analyze and produce a comprehensive activation checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing activation checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the activation checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the activation checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Activation Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/aha-moment-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/product/aha-moment-analysis/SKILL.md new file mode 100644 index 0000000..eb4cab3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/aha-moment-analysis/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a aha moment analysis with structured process, quality checks, and system integration +--- + +# Aha Moment Analysis + +## Purpose + +Analyze and produce a comprehensive aha moment analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing aha moment analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the aha moment analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the aha moment analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Aha Moment Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/analytics-implementation/SKILL.md b/clowdex-download/.claude/.claude/skills/product/analytics-implementation/SKILL.md new file mode 100644 index 0000000..e59af1b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/analytics-implementation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a analytics implementation with structured process, quality checks, and system integration +--- + +# Analytics Implementation + +## Purpose + +Create a comprehensive analytics implementation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing analytics implementation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the analytics implementation +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the analytics implementation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Analytics Implementation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/api-product-design/SKILL.md b/clowdex-download/.claude/.claude/skills/product/api-product-design/SKILL.md new file mode 100644 index 0000000..64456b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/api-product-design/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a api product design with structured process, quality checks, and system integration +--- + +# Api Product Design + +## Purpose + +Create a comprehensive api product design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing api product design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the api product design +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the api product design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Api Product Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/beta-program-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/beta-program-plan/SKILL.md new file mode 100644 index 0000000..55788c6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/beta-program-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a beta program plan with structured process, quality checks, and system integration +--- + +# Beta Program Plan + +## Purpose + +Design and document a comprehensive beta program plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing beta program plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the beta program plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the beta program plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Beta Program Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/board-product-update/SKILL.md b/clowdex-download/.claude/.claude/skills/product/board-product-update/SKILL.md new file mode 100644 index 0000000..a5eaeb4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/board-product-update/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a board product update with structured process, quality checks, and system integration +--- + +# Board Product Update + +## Purpose + +Create a comprehensive board product update that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board product update documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board product update +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board product update using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Board Product Update + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/bug-triage/SKILL.md b/clowdex-download/.claude/.claude/skills/product/bug-triage/SKILL.md new file mode 100644 index 0000000..39889f6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/bug-triage/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a bug triage with structured process, quality checks, and system integration +--- + +# Bug Triage + +## Purpose + +Create a comprehensive bug triage that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bug triage documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bug triage +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bug triage using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Bug Triage + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/changelog-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/product/changelog-writer/SKILL.md new file mode 100644 index 0000000..6a8474c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/changelog-writer/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a changelog writer with structured process, quality checks, and system integration +--- + +# Changelog Writer + +## Purpose + +Create a comprehensive changelog writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing changelog writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the changelog writer +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the changelog writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Changelog Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/competitive-product-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/product/competitive-product-analysis/SKILL.md new file mode 100644 index 0000000..c9122a0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/competitive-product-analysis/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a competitive product analysis with structured process, quality checks, and system integration +--- + +# Competitive Product Analysis + +## Purpose + +Analyze and produce a comprehensive competitive product analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitive product analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitive product analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitive product analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Competitive Product Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/data-taxonomy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/data-taxonomy/SKILL.md new file mode 100644 index 0000000..f540dc7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/data-taxonomy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a data taxonomy with structured process, quality checks, and system integration +--- + +# Data Taxonomy + +## Purpose + +Create a comprehensive data taxonomy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data taxonomy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data taxonomy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data taxonomy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Data Taxonomy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/deprecation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/deprecation-plan/SKILL.md new file mode 100644 index 0000000..294795e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/deprecation-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a deprecation plan with structured process, quality checks, and system integration +--- + +# Deprecation Plan + +## Purpose + +Design and document a comprehensive deprecation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deprecation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deprecation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deprecation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Deprecation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/early-adopter-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/early-adopter-strategy/SKILL.md new file mode 100644 index 0000000..28919f6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/early-adopter-strategy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a early adopter strategy with structured process, quality checks, and system integration +--- + +# Early Adopter Strategy + +## Purpose + +Design and document a comprehensive early adopter strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing early adopter strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the early adopter strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the early adopter strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Early Adopter Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/ecosystem-map/SKILL.md b/clowdex-download/.claude/.claude/skills/product/ecosystem-map/SKILL.md new file mode 100644 index 0000000..c412b12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/ecosystem-map/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a ecosystem map with structured process, quality checks, and system integration +--- + +# Ecosystem Map + +## Purpose + +Design and document a comprehensive ecosystem map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ecosystem map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ecosystem map +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ecosystem map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Ecosystem Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/empathy-map/SKILL.md b/clowdex-download/.claude/.claude/skills/product/empathy-map/SKILL.md new file mode 100644 index 0000000..c50d645 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/empathy-map/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a empathy map with structured process, quality checks, and system integration +--- + +# Empathy Map + +## Purpose + +Create a comprehensive empathy map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing empathy map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the empathy map +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the empathy map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Empathy Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/event-tracking-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/event-tracking-plan/SKILL.md new file mode 100644 index 0000000..11f131b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/event-tracking-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a event tracking plan with structured process, quality checks, and system integration +--- + +# Event Tracking Plan + +## Purpose + +Design and document a comprehensive event tracking plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event tracking plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event tracking plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event tracking plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Event Tracking Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/experiment-design/SKILL.md b/clowdex-download/.claude/.claude/skills/product/experiment-design/SKILL.md new file mode 100644 index 0000000..af1c144 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/experiment-design/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a experiment design with structured process, quality checks, and system integration +--- + +# Experiment Design + +## Purpose + +Create a comprehensive experiment design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing experiment design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the experiment design +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the experiment design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Experiment Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/faq-builder/SKILL.md b/clowdex-download/.claude/.claude/skills/product/faq-builder/SKILL.md new file mode 100644 index 0000000..55e14df --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/faq-builder/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a faq builder with structured process, quality checks, and system integration +--- + +# Faq Builder + +## Purpose + +Create a comprehensive faq builder that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing faq builder documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the faq builder +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the faq builder using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Faq Builder + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feature-comparison-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feature-comparison-matrix/SKILL.md new file mode 100644 index 0000000..142024c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feature-comparison-matrix/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a feature comparison matrix with structured process, quality checks, and system integration +--- + +# Feature Comparison Matrix + +## Purpose + +Analyze and produce a comprehensive feature comparison matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature comparison matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature comparison matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature comparison matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feature Comparison Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feature-flag-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feature-flag-strategy/SKILL.md new file mode 100644 index 0000000..2cf75f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feature-flag-strategy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a feature flag strategy with structured process, quality checks, and system integration +--- + +# Feature Flag Strategy + +## Purpose + +Design and document a comprehensive feature flag strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature flag strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature flag strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature flag strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feature Flag Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feature-prioritization/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feature-prioritization/SKILL.md new file mode 100644 index 0000000..0d60867 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feature-prioritization/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a feature prioritization with structured process, quality checks, and system integration +--- + +# Feature Prioritization + +## Purpose + +Create a comprehensive feature prioritization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature prioritization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature prioritization +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature prioritization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feature Prioritization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feature-request-triage/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feature-request-triage/SKILL.md new file mode 100644 index 0000000..bb88ed9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feature-request-triage/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a feature request triage with structured process, quality checks, and system integration +--- + +# Feature Request Triage + +## Purpose + +Create a comprehensive feature request triage that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature request triage documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature request triage +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature request triage using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feature Request Triage + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feature-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feature-roadmap/SKILL.md new file mode 100644 index 0000000..01cbe3b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feature-roadmap/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a feature roadmap with structured process, quality checks, and system integration +--- + +# Feature Roadmap + +## Purpose + +Design and document a comprehensive feature roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feature roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feature roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feature roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feature Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/feedback-taxonomy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/feedback-taxonomy/SKILL.md new file mode 100644 index 0000000..142245f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/feedback-taxonomy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a feedback taxonomy with structured process, quality checks, and system integration +--- + +# Feedback Taxonomy + +## Purpose + +Create a comprehensive feedback taxonomy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing feedback taxonomy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the feedback taxonomy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the feedback taxonomy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Feedback Taxonomy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/freemium-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/freemium-strategy/SKILL.md new file mode 100644 index 0000000..783e4c7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/freemium-strategy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a freemium strategy with structured process, quality checks, and system integration +--- + +# Freemium Strategy + +## Purpose + +Design and document a comprehensive freemium strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing freemium strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the freemium strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the freemium strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Freemium Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/impact-effort-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/product/impact-effort-matrix/SKILL.md new file mode 100644 index 0000000..fe0df9b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/impact-effort-matrix/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a impact effort matrix with structured process, quality checks, and system integration +--- + +# Impact Effort Matrix + +## Purpose + +Create a comprehensive impact effort matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing impact effort matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the impact effort matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the impact effort matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Impact Effort Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/job-to-be-done/SKILL.md b/clowdex-download/.claude/.claude/skills/product/job-to-be-done/SKILL.md new file mode 100644 index 0000000..e943ad9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/job-to-be-done/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a job to be done with structured process, quality checks, and system integration +--- + +# Job To Be Done + +## Purpose + +Create a comprehensive job to be done that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing job to be done documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the job to be done +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the job to be done using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Job To Be Done + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/knowledge-base-article/SKILL.md b/clowdex-download/.claude/.claude/skills/product/knowledge-base-article/SKILL.md new file mode 100644 index 0000000..24c7c96 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/knowledge-base-article/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a knowledge base article with structured process, quality checks, and system integration +--- + +# Knowledge Base Article + +## Purpose + +Create a comprehensive knowledge base article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing knowledge base article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the knowledge base article +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the knowledge base article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Knowledge Base Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/migration-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/migration-plan/SKILL.md new file mode 100644 index 0000000..439cce0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/migration-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a migration plan with structured process, quality checks, and system integration +--- + +# Migration Plan + +## Purpose + +Design and document a comprehensive migration plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing migration plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the migration plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the migration plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Migration Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/north-star-metric/SKILL.md b/clowdex-download/.claude/.claude/skills/product/north-star-metric/SKILL.md new file mode 100644 index 0000000..5b8038a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/north-star-metric/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a north star metric with structured process, quality checks, and system integration +--- + +# North Star Metric + +## Purpose + +Create a comprehensive north star metric that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing north star metric documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the north star metric +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the north star metric using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# North Star Metric + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/persona-creation/SKILL.md b/clowdex-download/.claude/.claude/skills/product/persona-creation/SKILL.md new file mode 100644 index 0000000..b2da592 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/persona-creation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a persona creation with structured process, quality checks, and system integration +--- + +# Persona Creation + +## Purpose + +Create a comprehensive persona creation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing persona creation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the persona creation +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the persona creation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Persona Creation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/pirate-metrics/SKILL.md b/clowdex-download/.claude/.claude/skills/product/pirate-metrics/SKILL.md new file mode 100644 index 0000000..f20e888 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/pirate-metrics/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a pirate metrics with structured process, quality checks, and system integration +--- + +# Pirate Metrics + +## Purpose + +Analyze and produce a comprehensive pirate metrics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pirate metrics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pirate metrics +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pirate metrics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Pirate Metrics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/platform-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/platform-strategy/SKILL.md new file mode 100644 index 0000000..0ca6758 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/platform-strategy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a platform strategy with structured process, quality checks, and system integration +--- + +# Platform Strategy + +## Purpose + +Design and document a comprehensive platform strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing platform strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the platform strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the platform strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Platform Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/positioning-map/SKILL.md b/clowdex-download/.claude/.claude/skills/product/positioning-map/SKILL.md new file mode 100644 index 0000000..41c07aa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/positioning-map/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a positioning map with structured process, quality checks, and system integration +--- + +# Positioning Map + +## Purpose + +Create a comprehensive positioning map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing positioning map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the positioning map +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the positioning map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Positioning Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/prd-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/product/prd-writer/SKILL.md new file mode 100644 index 0000000..4b47c56 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/prd-writer/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a prd writer with structured process, quality checks, and system integration +--- + +# Prd Writer + +## Purpose + +Create a comprehensive prd writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing prd writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the prd writer +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the prd writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Prd Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/pricing-model/SKILL.md b/clowdex-download/.claude/.claude/skills/product/pricing-model/SKILL.md new file mode 100644 index 0000000..2e2a510 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/pricing-model/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a pricing model with structured process, quality checks, and system integration +--- + +# Pricing Model + +## Purpose + +Design and document a comprehensive pricing model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing model +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Pricing Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-brief/SKILL.md new file mode 100644 index 0000000..68d7920 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-brief/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product brief with structured process, quality checks, and system integration +--- + +# Product Brief + +## Purpose + +Create a comprehensive product brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product brief +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-council-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-council-deck/SKILL.md new file mode 100644 index 0000000..26570f8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-council-deck/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product council deck with structured process, quality checks, and system integration +--- + +# Product Council Deck + +## Purpose + +Create a comprehensive product council deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product council deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product council deck +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product council deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Council Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-documentation/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-documentation/SKILL.md new file mode 100644 index 0000000..ab45592 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-documentation/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product documentation with structured process, quality checks, and system integration +--- + +# Product Documentation + +## Purpose + +Create a comprehensive product documentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product documentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product documentation +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product documentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Documentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-health-check/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-health-check/SKILL.md new file mode 100644 index 0000000..a65676f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-health-check/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a product health check with structured process, quality checks, and system integration +--- + +# Product Health Check + +## Purpose + +Analyze and produce a comprehensive product health check that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product health check documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product health check +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product health check using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Health Check + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-launch-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-launch-brief/SKILL.md new file mode 100644 index 0000000..b4a1c8c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-launch-brief/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product launch brief with structured process, quality checks, and system integration +--- + +# Product Launch Brief + +## Purpose + +Create a comprehensive product launch brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product launch brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product launch brief +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product launch brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Launch Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-metrics-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-metrics-framework/SKILL.md new file mode 100644 index 0000000..f7c648c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-metrics-framework/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a product metrics framework with structured process, quality checks, and system integration +--- + +# Product Metrics Framework + +## Purpose + +Analyze and produce a comprehensive product metrics framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product metrics framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product metrics framework +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product metrics framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Metrics Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-onboarding-flow/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-onboarding-flow/SKILL.md new file mode 100644 index 0000000..0530176 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-onboarding-flow/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product onboarding flow with structured process, quality checks, and system integration +--- + +# Product Onboarding Flow + +## Purpose + +Create a comprehensive product onboarding flow that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product onboarding flow documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product onboarding flow +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product onboarding flow using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Onboarding Flow + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-one-pager/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-one-pager/SKILL.md new file mode 100644 index 0000000..e745a32 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-one-pager/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product one pager with structured process, quality checks, and system integration +--- + +# Product One Pager + +## Purpose + +Create a comprehensive product one pager that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product one pager documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product one pager +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product one pager using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product One Pager + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-principles/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-principles/SKILL.md new file mode 100644 index 0000000..944a2e1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-principles/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product principles with structured process, quality checks, and system integration +--- + +# Product Principles + +## Purpose + +Create a comprehensive product principles that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product principles documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product principles +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product principles using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Principles + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-retrospective/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-retrospective/SKILL.md new file mode 100644 index 0000000..bde55e4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-retrospective/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product retrospective with structured process, quality checks, and system integration +--- + +# Product Retrospective + +## Purpose + +Create a comprehensive product retrospective that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product retrospective documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product retrospective +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product retrospective using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Retrospective + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-review/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-review/SKILL.md new file mode 100644 index 0000000..b941b88 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-review/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a product review with structured process, quality checks, and system integration +--- + +# Product Review + +## Purpose + +Analyze and produce a comprehensive product review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product review +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-roadmap/SKILL.md new file mode 100644 index 0000000..47d8286 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-roadmap/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a product roadmap with structured process, quality checks, and system integration +--- + +# Product Roadmap + +## Purpose + +Design and document a comprehensive product roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-strategy/SKILL.md new file mode 100644 index 0000000..9b014d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-strategy/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a product strategy with structured process, quality checks, and system integration +--- + +# Product Strategy + +## Purpose + +Design and document a comprehensive product strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/product-vision/SKILL.md b/clowdex-download/.claude/.claude/skills/product/product-vision/SKILL.md new file mode 100644 index 0000000..7351078 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/product-vision/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a product vision with structured process, quality checks, and system integration +--- + +# Product Vision + +## Purpose + +Create a comprehensive product vision that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product vision documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product vision +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product vision using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Product Vision + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/release-notes-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/product/release-notes-writer/SKILL.md new file mode 100644 index 0000000..61ba9e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/release-notes-writer/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a release notes writer with structured process, quality checks, and system integration +--- + +# Release Notes Writer + +## Purpose + +Create a comprehensive release notes writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing release notes writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the release notes writer +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the release notes writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Release Notes Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/release-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/product/release-planning/SKILL.md new file mode 100644 index 0000000..a2d7f0f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/release-planning/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a release planning with structured process, quality checks, and system integration +--- + +# Release Planning + +## Purpose + +Design and document a comprehensive release planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing release planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the release planning +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the release planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Release Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/rice-scoring/SKILL.md b/clowdex-download/.claude/.claude/skills/product/rice-scoring/SKILL.md new file mode 100644 index 0000000..84a5bea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/rice-scoring/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Analyze and produce a rice scoring with structured process, quality checks, and system integration +--- + +# Rice Scoring + +## Purpose + +Analyze and produce a comprehensive rice scoring that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rice scoring documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rice scoring +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rice scoring using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Rice Scoring + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/stakeholder-update/SKILL.md b/clowdex-download/.claude/.claude/skills/product/stakeholder-update/SKILL.md new file mode 100644 index 0000000..2febe81 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/stakeholder-update/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a stakeholder update with structured process, quality checks, and system integration +--- + +# Stakeholder Update + +## Purpose + +Create a comprehensive stakeholder update that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing stakeholder update documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the stakeholder update +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the stakeholder update using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Stakeholder Update + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/technical-debt-prioritization/SKILL.md b/clowdex-download/.claude/.claude/skills/product/technical-debt-prioritization/SKILL.md new file mode 100644 index 0000000..a68ba1e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/technical-debt-prioritization/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a technical debt prioritization with structured process, quality checks, and system integration +--- + +# Technical Debt Prioritization + +## Purpose + +Create a comprehensive technical debt prioritization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technical debt prioritization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technical debt prioritization +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technical debt prioritization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Technical Debt Prioritization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/technology-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/product/technology-roadmap/SKILL.md new file mode 100644 index 0000000..154ac15 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/technology-roadmap/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a technology roadmap with structured process, quality checks, and system integration +--- + +# Technology Roadmap + +## Purpose + +Design and document a comprehensive technology roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technology roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technology roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technology roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Technology Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/trial-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/product/trial-optimization/SKILL.md new file mode 100644 index 0000000..2cc94e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/trial-optimization/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a trial optimization with structured process, quality checks, and system integration +--- + +# Trial Optimization + +## Purpose + +Create a comprehensive trial optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trial optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trial optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trial optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Trial Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/usability-test-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/usability-test-plan/SKILL.md new file mode 100644 index 0000000..feb500b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/usability-test-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a usability test plan with structured process, quality checks, and system integration +--- + +# Usability Test Plan + +## Purpose + +Design and document a comprehensive usability test plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing usability test plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the usability test plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the usability test plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# Usability Test Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/user-interview-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/product/user-interview-guide/SKILL.md new file mode 100644 index 0000000..89cf968 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/user-interview-guide/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a user interview guide with structured process, quality checks, and system integration +--- + +# User Interview Guide + +## Purpose + +Design and document a comprehensive user interview guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user interview guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user interview guide +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user interview guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# User Interview Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/user-journey-map/SKILL.md b/clowdex-download/.claude/.claude/skills/product/user-journey-map/SKILL.md new file mode 100644 index 0000000..dda5d72 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/user-journey-map/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a user journey map with structured process, quality checks, and system integration +--- + +# User Journey Map + +## Purpose + +Create a comprehensive user journey map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user journey map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user journey map +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user journey map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# User Journey Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/user-research-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/product/user-research-plan/SKILL.md new file mode 100644 index 0000000..2d9e8c6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/user-research-plan/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Design and document a user research plan with structured process, quality checks, and system integration +--- + +# User Research Plan + +## Purpose + +Design and document a comprehensive user research plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user research plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user research plan +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user research plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# User Research Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/product/user-story/SKILL.md b/clowdex-download/.claude/.claude/skills/product/user-story/SKILL.md new file mode 100644 index 0000000..07eb985 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/product/user-story/SKILL.md @@ -0,0 +1,135 @@ +--- +description: Create a user story with structured process, quality checks, and system integration +--- + +# User Story + +## Purpose + +Create a comprehensive user story that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Product Management + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Product/Feature**: What product or feature this relates to + +### Optional +- **User Research**: Existing insights or data +- **Constraints**: Technical, timeline, or resource limitations + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user story documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Jobs To Be Done, Kano Model, RICE Scoring + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user story +- Identify gaps, opportunities, and risks +- Define success metrics: Activation Rate, Feature Adoption, Daily/Monthly Active Users, Retention (D1/D7/D30) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user story using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 5 users before building anything + +## Output Format + +```markdown +# User Story + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Jobs To Be Done +- Kano Model +- RICE Scoring +- MoSCoW Prioritization +- Double Diamond +- Build-Measure-Learn +- Product-Led Growth +- AARRR (Pirate Metrics) + +## Key Metrics +- Activation Rate +- Feature Adoption +- Daily/Monthly Active Users +- Retention (D1/D7/D30) +- Net Revenue Retention +- Time to Value +- Customer Effort Score + +## Best Practices +- Talk to 5 users before building anything +- One metric that matters per quarter +- Ship small and iterate — 2-week max cycles +- Always define success criteria before building +- Kill features that less than 10% of users use + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/annual-goals/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/annual-goals/SKILL.md new file mode 100644 index 0000000..0243d8b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/annual-goals/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a annual goals with structured process, quality checks, and system integration +--- + +# Annual Goals + +## Purpose + +Create a comprehensive annual goals that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing annual goals documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the annual goals +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the annual goals using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Annual Goals + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/bio-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/bio-writer/SKILL.md new file mode 100644 index 0000000..cdbe15d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/bio-writer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a bio writer with structured process, quality checks, and system integration +--- + +# Bio Writer + +## Purpose + +Create a comprehensive bio writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bio writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bio writer +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bio writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Bio Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/book-summary/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/book-summary/SKILL.md new file mode 100644 index 0000000..29ed385 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/book-summary/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a book summary with structured process, quality checks, and system integration +--- + +# Book Summary + +## Purpose + +Create a comprehensive book summary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing book summary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the book summary +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the book summary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Book Summary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/boundary-setting/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/boundary-setting/SKILL.md new file mode 100644 index 0000000..f40c7a1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/boundary-setting/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a boundary setting with structured process, quality checks, and system integration +--- + +# Boundary Setting + +## Purpose + +Create a comprehensive boundary setting that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing boundary setting documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the boundary setting +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the boundary setting using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Boundary Setting + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/burnout-prevention/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/burnout-prevention/SKILL.md new file mode 100644 index 0000000..1bfd5e7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/burnout-prevention/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a burnout prevention with structured process, quality checks, and system integration +--- + +# Burnout Prevention + +## Purpose + +Create a comprehensive burnout prevention that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing burnout prevention documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the burnout prevention +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the burnout prevention using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Burnout Prevention + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/career-development/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/career-development/SKILL.md new file mode 100644 index 0000000..1217e76 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/career-development/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a career development with structured process, quality checks, and system integration +--- + +# Career Development + +## Purpose + +Create a comprehensive career development that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing career development documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the career development +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the career development using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Career Development + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/career-pivot-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/career-pivot-plan/SKILL.md new file mode 100644 index 0000000..173f91e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/career-pivot-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a career pivot plan with structured process, quality checks, and system integration +--- + +# Career Pivot Plan + +## Purpose + +Design and document a comprehensive career pivot plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing career pivot plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the career pivot plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the career pivot plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Career Pivot Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/consulting-rate-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/consulting-rate-calculator/SKILL.md new file mode 100644 index 0000000..6e3774a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/consulting-rate-calculator/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a consulting rate calculator with structured process, quality checks, and system integration +--- + +# Consulting Rate Calculator + +## Purpose + +Create a comprehensive consulting rate calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing consulting rate calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the consulting rate calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the consulting rate calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Consulting Rate Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/cover-letter/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/cover-letter/SKILL.md new file mode 100644 index 0000000..3021b26 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/cover-letter/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a cover letter with structured process, quality checks, and system integration +--- + +# Cover Letter + +## Purpose + +Create a comprehensive cover letter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cover letter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cover letter +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cover letter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Cover Letter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/daily-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/daily-planning/SKILL.md new file mode 100644 index 0000000..b0afd4a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/daily-planning/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a daily planning with structured process, quality checks, and system integration +--- + +# Daily Planning + +## Purpose + +Design and document a comprehensive daily planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing daily planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the daily planning +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the daily planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Daily Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/decision-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/decision-matrix/SKILL.md new file mode 100644 index 0000000..825a82c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/decision-matrix/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a decision matrix with structured process, quality checks, and system integration +--- + +# Decision Matrix + +## Purpose + +Create a comprehensive decision matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing decision matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the decision matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the decision matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Decision Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/deep-work-blocks/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/deep-work-blocks/SKILL.md new file mode 100644 index 0000000..6ccfcac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/deep-work-blocks/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a deep work blocks with structured process, quality checks, and system integration +--- + +# Deep Work Blocks + +## Purpose + +Create a comprehensive deep work blocks that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deep work blocks documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deep work blocks +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deep work blocks using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Deep Work Blocks + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/delegation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/delegation-plan/SKILL.md new file mode 100644 index 0000000..6bb8e6c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/delegation-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a delegation plan with structured process, quality checks, and system integration +--- + +# Delegation Plan + +## Purpose + +Design and document a comprehensive delegation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing delegation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the delegation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the delegation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Delegation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/eisenhower-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/eisenhower-matrix/SKILL.md new file mode 100644 index 0000000..1fe8526 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/eisenhower-matrix/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a eisenhower matrix with structured process, quality checks, and system integration +--- + +# Eisenhower Matrix + +## Purpose + +Create a comprehensive eisenhower matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing eisenhower matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the eisenhower matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the eisenhower matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Eisenhower Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/email-management/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/email-management/SKILL.md new file mode 100644 index 0000000..a389441 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/email-management/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a email management with structured process, quality checks, and system integration +--- + +# Email Management + +## Purpose + +Create a comprehensive email management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email management +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Email Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/email-template-library/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/email-template-library/SKILL.md new file mode 100644 index 0000000..48a108f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/email-template-library/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a email template library with structured process, quality checks, and system integration +--- + +# Email Template Library + +## Purpose + +Create a comprehensive email template library that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing email template library documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the email template library +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the email template library using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Email Template Library + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/energy-management/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/energy-management/SKILL.md new file mode 100644 index 0000000..2153300 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/energy-management/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a energy management with structured process, quality checks, and system integration +--- + +# Energy Management + +## Purpose + +Create a comprehensive energy management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing energy management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the energy management +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the energy management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Energy Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/follow-up-system/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/follow-up-system/SKILL.md new file mode 100644 index 0000000..57dbcdb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/follow-up-system/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a follow up system with structured process, quality checks, and system integration +--- + +# Follow Up System + +## Purpose + +Design and document a comprehensive follow up system that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing follow up system documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the follow up system +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the follow up system using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Follow Up System + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/freelance-proposal/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/freelance-proposal/SKILL.md new file mode 100644 index 0000000..3a4a5b7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/freelance-proposal/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a freelance proposal with structured process, quality checks, and system integration +--- + +# Freelance Proposal + +## Purpose + +Create a comprehensive freelance proposal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing freelance proposal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the freelance proposal +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the freelance proposal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Freelance Proposal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/goal-setting-okr/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/goal-setting-okr/SKILL.md new file mode 100644 index 0000000..7f2bfda --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/goal-setting-okr/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a goal setting okr with structured process, quality checks, and system integration +--- + +# Goal Setting Okr + +## Purpose + +Create a comprehensive goal setting okr that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing goal setting okr documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the goal setting okr +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the goal setting okr using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Goal Setting Okr + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/gratitude-practice/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/gratitude-practice/SKILL.md new file mode 100644 index 0000000..4bbed5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/gratitude-practice/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a gratitude practice with structured process, quality checks, and system integration +--- + +# Gratitude Practice + +## Purpose + +Create a comprehensive gratitude practice that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing gratitude practice documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the gratitude practice +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the gratitude practice using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Gratitude Practice + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/habit-stack-design/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/habit-stack-design/SKILL.md new file mode 100644 index 0000000..1720e06 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/habit-stack-design/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a habit stack design with structured process, quality checks, and system integration +--- + +# Habit Stack Design + +## Purpose + +Create a comprehensive habit stack design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing habit stack design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the habit stack design +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the habit stack design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Habit Stack Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/habit-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/habit-tracker/SKILL.md new file mode 100644 index 0000000..929cb74 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/habit-tracker/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a habit tracker with structured process, quality checks, and system integration +--- + +# Habit Tracker + +## Purpose + +Analyze and produce a comprehensive habit tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing habit tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the habit tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the habit tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Habit Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/inbox-zero-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/inbox-zero-plan/SKILL.md new file mode 100644 index 0000000..81d7986 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/inbox-zero-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a inbox zero plan with structured process, quality checks, and system integration +--- + +# Inbox Zero Plan + +## Purpose + +Design and document a comprehensive inbox zero plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing inbox zero plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the inbox zero plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the inbox zero plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Inbox Zero Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/journal-prompts/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/journal-prompts/SKILL.md new file mode 100644 index 0000000..ca8915c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/journal-prompts/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a journal prompts with structured process, quality checks, and system integration +--- + +# Journal Prompts + +## Purpose + +Create a comprehensive journal prompts that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing journal prompts documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the journal prompts +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the journal prompts using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Journal Prompts + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/learning-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/learning-plan/SKILL.md new file mode 100644 index 0000000..ed59cd8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/learning-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a learning plan with structured process, quality checks, and system integration +--- + +# Learning Plan + +## Purpose + +Design and document a comprehensive learning plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing learning plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the learning plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the learning plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Learning Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/linkedin-profile-rewrite/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/linkedin-profile-rewrite/SKILL.md new file mode 100644 index 0000000..09855a3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/linkedin-profile-rewrite/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin profile rewrite with structured process, quality checks, and system integration +--- + +# Linkedin Profile Rewrite + +## Purpose + +Create a comprehensive linkedin profile rewrite that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin profile rewrite documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin profile rewrite +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin profile rewrite using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Linkedin Profile Rewrite + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/linkedin-recommendation/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/linkedin-recommendation/SKILL.md new file mode 100644 index 0000000..cc38dd7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/linkedin-recommendation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin recommendation with structured process, quality checks, and system integration +--- + +# Linkedin Recommendation + +## Purpose + +Create a comprehensive linkedin recommendation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin recommendation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin recommendation +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin recommendation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Linkedin Recommendation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/meeting-agenda-personal/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/meeting-agenda-personal/SKILL.md new file mode 100644 index 0000000..a2a016f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/meeting-agenda-personal/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a meeting agenda personal with structured process, quality checks, and system integration +--- + +# Meeting Agenda Personal + +## Purpose + +Create a comprehensive meeting agenda personal that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting agenda personal documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting agenda personal +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting agenda personal using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Meeting Agenda Personal + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/meeting-notes-summary/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/meeting-notes-summary/SKILL.md new file mode 100644 index 0000000..e0bf594 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/meeting-notes-summary/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a meeting notes summary with structured process, quality checks, and system integration +--- + +# Meeting Notes Summary + +## Purpose + +Create a comprehensive meeting notes summary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting notes summary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting notes summary +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting notes summary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Meeting Notes Summary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/meeting-optimizer/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/meeting-optimizer/SKILL.md new file mode 100644 index 0000000..e5b9a66 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/meeting-optimizer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a meeting optimizer with structured process, quality checks, and system integration +--- + +# Meeting Optimizer + +## Purpose + +Create a comprehensive meeting optimizer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meeting optimizer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meeting optimizer +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meeting optimizer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Meeting Optimizer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/mit-method/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/mit-method/SKILL.md new file mode 100644 index 0000000..c3a0978 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/mit-method/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a mit method with structured process, quality checks, and system integration +--- + +# Mit Method + +## Purpose + +Create a comprehensive mit method that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mit method documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mit method +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mit method using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Mit Method + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/networking-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/networking-strategy/SKILL.md new file mode 100644 index 0000000..f00e377 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/networking-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a networking strategy with structured process, quality checks, and system integration +--- + +# Networking Strategy + +## Purpose + +Design and document a comprehensive networking strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing networking strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the networking strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the networking strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Networking Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/outsourcing-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/outsourcing-evaluation/SKILL.md new file mode 100644 index 0000000..4fcd516 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/outsourcing-evaluation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a outsourcing evaluation with structured process, quality checks, and system integration +--- + +# Outsourcing Evaluation + +## Purpose + +Analyze and produce a comprehensive outsourcing evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing outsourcing evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the outsourcing evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the outsourcing evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Outsourcing Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/peak-performance-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/peak-performance-schedule/SKILL.md new file mode 100644 index 0000000..06ffd3c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/peak-performance-schedule/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a peak performance schedule with structured process, quality checks, and system integration +--- + +# Peak Performance Schedule + +## Purpose + +Design and document a comprehensive peak performance schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing peak performance schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the peak performance schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the peak performance schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Peak Performance Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/personal-brand-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/personal-brand-audit/SKILL.md new file mode 100644 index 0000000..866f489 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/personal-brand-audit/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a personal brand audit with structured process, quality checks, and system integration +--- + +# Personal Brand Audit + +## Purpose + +Analyze and produce a comprehensive personal brand audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing personal brand audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the personal brand audit +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the personal brand audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Personal Brand Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/presentation-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/presentation-outline/SKILL.md new file mode 100644 index 0000000..102482f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/presentation-outline/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a presentation outline with structured process, quality checks, and system integration +--- + +# Presentation Outline + +## Purpose + +Create a comprehensive presentation outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing presentation outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the presentation outline +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the presentation outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Presentation Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/priority-matrix/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/priority-matrix/SKILL.md new file mode 100644 index 0000000..14a67c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/priority-matrix/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a priority matrix with structured process, quality checks, and system integration +--- + +# Priority Matrix + +## Purpose + +Create a comprehensive priority matrix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing priority matrix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the priority matrix +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the priority matrix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Priority Matrix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/project-breakdown/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/project-breakdown/SKILL.md new file mode 100644 index 0000000..e7c6a42 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/project-breakdown/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a project breakdown with structured process, quality checks, and system integration +--- + +# Project Breakdown + +## Purpose + +Create a comprehensive project breakdown that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project breakdown documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project breakdown +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project breakdown using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Project Breakdown + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/pros-cons-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/pros-cons-analysis/SKILL.md new file mode 100644 index 0000000..3b1a144 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/pros-cons-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a pros cons analysis with structured process, quality checks, and system integration +--- + +# Pros Cons Analysis + +## Purpose + +Analyze and produce a comprehensive pros cons analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pros cons analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pros cons analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pros cons analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Pros Cons Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/public-speaking-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/public-speaking-prep/SKILL.md new file mode 100644 index 0000000..a9b0f37 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/public-speaking-prep/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a public speaking prep with structured process, quality checks, and system integration +--- + +# Public Speaking Prep + +## Purpose + +Create a comprehensive public speaking prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing public speaking prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the public speaking prep +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the public speaking prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Public Speaking Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/quarterly-goals/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/quarterly-goals/SKILL.md new file mode 100644 index 0000000..c88a248 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/quarterly-goals/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a quarterly goals with structured process, quality checks, and system integration +--- + +# Quarterly Goals + +## Purpose + +Create a comprehensive quarterly goals that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quarterly goals documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quarterly goals +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quarterly goals using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Quarterly Goals + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/reflection-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/reflection-framework/SKILL.md new file mode 100644 index 0000000..fb12771 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/reflection-framework/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a reflection framework with structured process, quality checks, and system integration +--- + +# Reflection Framework + +## Purpose + +Design and document a comprehensive reflection framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reflection framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reflection framework +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reflection framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Reflection Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/relationship-management/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/relationship-management/SKILL.md new file mode 100644 index 0000000..675a011 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/relationship-management/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a relationship management with structured process, quality checks, and system integration +--- + +# Relationship Management + +## Purpose + +Create a comprehensive relationship management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing relationship management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the relationship management +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the relationship management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Relationship Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/resume-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/resume-writer/SKILL.md new file mode 100644 index 0000000..d211ac1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/resume-writer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a resume writer with structured process, quality checks, and system integration +--- + +# Resume Writer + +## Purpose + +Create a comprehensive resume writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing resume writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the resume writer +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the resume writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Resume Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/routine-optimizer/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/routine-optimizer/SKILL.md new file mode 100644 index 0000000..de466c7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/routine-optimizer/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a routine optimizer with structured process, quality checks, and system integration +--- + +# Routine Optimizer + +## Purpose + +Create a comprehensive routine optimizer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing routine optimizer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the routine optimizer +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the routine optimizer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Routine Optimizer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/salary-negotiation/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/salary-negotiation/SKILL.md new file mode 100644 index 0000000..74b946e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/salary-negotiation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a salary negotiation with structured process, quality checks, and system integration +--- + +# Salary Negotiation + +## Purpose + +Create a comprehensive salary negotiation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing salary negotiation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the salary negotiation +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the salary negotiation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Salary Negotiation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/side-project-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/side-project-plan/SKILL.md new file mode 100644 index 0000000..93e2334 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/side-project-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a side project plan with structured process, quality checks, and system integration +--- + +# Side Project Plan + +## Purpose + +Design and document a comprehensive side project plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing side project plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the side project plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the side project plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Side Project Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/skill-acquisition-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/skill-acquisition-plan/SKILL.md new file mode 100644 index 0000000..2530115 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/skill-acquisition-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a skill acquisition plan with structured process, quality checks, and system integration +--- + +# Skill Acquisition Plan + +## Purpose + +Design and document a comprehensive skill acquisition plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing skill acquisition plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the skill acquisition plan +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the skill acquisition plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Skill Acquisition Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/storytelling-framework/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/storytelling-framework/SKILL.md new file mode 100644 index 0000000..7615c6f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/storytelling-framework/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a storytelling framework with structured process, quality checks, and system integration +--- + +# Storytelling Framework + +## Purpose + +Design and document a comprehensive storytelling framework that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing storytelling framework documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the storytelling framework +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the storytelling framework using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Storytelling Framework + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/task-decomposition/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/task-decomposition/SKILL.md new file mode 100644 index 0000000..0bfb040 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/task-decomposition/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a task decomposition with structured process, quality checks, and system integration +--- + +# Task Decomposition + +## Purpose + +Create a comprehensive task decomposition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing task decomposition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the task decomposition +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the task decomposition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Task Decomposition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/time-blocking/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/time-blocking/SKILL.md new file mode 100644 index 0000000..dee80c4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/time-blocking/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a time blocking with structured process, quality checks, and system integration +--- + +# Time Blocking + +## Purpose + +Create a comprehensive time blocking that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing time blocking documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the time blocking +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the time blocking using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Time Blocking + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/virtual-assistant-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/virtual-assistant-brief/SKILL.md new file mode 100644 index 0000000..a8869c0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/virtual-assistant-brief/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a virtual assistant brief with structured process, quality checks, and system integration +--- + +# Virtual Assistant Brief + +## Purpose + +Create a comprehensive virtual assistant brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing virtual assistant brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the virtual assistant brief +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the virtual assistant brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Virtual Assistant Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/weekly-review/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/weekly-review/SKILL.md new file mode 100644 index 0000000..b2c2a67 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/weekly-review/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a weekly review with structured process, quality checks, and system integration +--- + +# Weekly Review + +## Purpose + +Analyze and produce a comprehensive weekly review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing weekly review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the weekly review +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the weekly review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Weekly Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/weighted-scoring/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/weighted-scoring/SKILL.md new file mode 100644 index 0000000..e9bdcb6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/weighted-scoring/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a weighted scoring with structured process, quality checks, and system integration +--- + +# Weighted Scoring + +## Purpose + +Analyze and produce a comprehensive weighted scoring that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing weighted scoring documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the weighted scoring +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the weighted scoring using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Weighted Scoring + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/work-breakdown-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/work-breakdown-structure/SKILL.md new file mode 100644 index 0000000..155fb91 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/work-breakdown-structure/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a work breakdown structure with structured process, quality checks, and system integration +--- + +# Work Breakdown Structure + +## Purpose + +Create a comprehensive work breakdown structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing work breakdown structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the work breakdown structure +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the work breakdown structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Work Breakdown Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/productivity/work-life-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/productivity/work-life-audit/SKILL.md new file mode 100644 index 0000000..be4c91f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/productivity/work-life-audit/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a work life audit with structured process, quality checks, and system integration +--- + +# Work Life Audit + +## Purpose + +Analyze and produce a comprehensive work life audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Personal Productivity + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing work life audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Getting Things Done (GTD), Eisenhower Matrix, Pomodoro Technique + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the work life audit +- Identify gaps, opportunities, and risks +- Define success metrics: Tasks Completed, Deep Work Hours, Meeting Load (%), Goal Progress +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the work life audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Most important task first, before email + +## Output Format + +```markdown +# Work Life Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Getting Things Done (GTD) +- Eisenhower Matrix +- Pomodoro Technique +- Time Blocking +- Weekly Review +- SMART Goals +- Deep Work + +## Key Metrics +- Tasks Completed +- Deep Work Hours +- Meeting Load (%) +- Goal Progress +- Energy Level +- Decision Quality + +## Best Practices +- Most important task first, before email +- Batch similar tasks together +- 2-minute rule: if it takes less, do it now +- Calendar audit monthly — eliminate 20% of meetings +- Weekly review on Friday, weekly plan on Sunday/Monday + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/1031-exchange-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/1031-exchange-guide/SKILL.md new file mode 100644 index 0000000..2bc71cd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/1031-exchange-guide/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a 1031 exchange guide with structured process, quality checks, and system integration +--- + +# 1031 Exchange Guide + +## Purpose + +Design and document a comprehensive 1031 exchange guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing 1031 exchange guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the 1031 exchange guide +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the 1031 exchange guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# 1031 Exchange Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/airbnb-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/airbnb-analysis/SKILL.md new file mode 100644 index 0000000..c35b528 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/airbnb-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a airbnb analysis with structured process, quality checks, and system integration +--- + +# Airbnb Analysis + +## Purpose + +Analyze and produce a comprehensive airbnb analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing airbnb analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the airbnb analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the airbnb analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Airbnb Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/asset-allocation-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/asset-allocation-re/SKILL.md new file mode 100644 index 0000000..3929446 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/asset-allocation-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a asset allocation re with structured process, quality checks, and system integration +--- + +# Asset Allocation Re + +## Purpose + +Create a comprehensive asset allocation re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing asset allocation re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the asset allocation re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the asset allocation re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Asset Allocation Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/buyer-consultation/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/buyer-consultation/SKILL.md new file mode 100644 index 0000000..3178f4e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/buyer-consultation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a buyer consultation with structured process, quality checks, and system integration +--- + +# Buyer Consultation + +## Purpose + +Create a comprehensive buyer consultation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing buyer consultation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the buyer consultation +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the buyer consultation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Buyer Consultation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/buyer-needs-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/buyer-needs-assessment/SKILL.md new file mode 100644 index 0000000..f7c37bc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/buyer-needs-assessment/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a buyer needs assessment with structured process, quality checks, and system integration +--- + +# Buyer Needs Assessment + +## Purpose + +Analyze and produce a comprehensive buyer needs assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing buyer needs assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the buyer needs assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the buyer needs assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Buyer Needs Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/cap-rate-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/cap-rate-analysis/SKILL.md new file mode 100644 index 0000000..0bad077 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/cap-rate-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a cap rate analysis with structured process, quality checks, and system integration +--- + +# Cap Rate Analysis + +## Purpose + +Analyze and produce a comprehensive cap rate analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cap rate analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cap rate analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cap rate analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Cap Rate Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/cash-on-cash-return/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/cash-on-cash-return/SKILL.md new file mode 100644 index 0000000..9707351 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/cash-on-cash-return/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a cash on cash return with structured process, quality checks, and system integration +--- + +# Cash On Cash Return + +## Purpose + +Create a comprehensive cash on cash return that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cash on cash return documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cash on cash return +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cash on cash return using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Cash On Cash Return + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/commercial-property-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/commercial-property-analysis/SKILL.md new file mode 100644 index 0000000..0a8cd45 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/commercial-property-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a commercial property analysis with structured process, quality checks, and system integration +--- + +# Commercial Property Analysis + +## Purpose + +Analyze and produce a comprehensive commercial property analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing commercial property analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the commercial property analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the commercial property analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Commercial Property Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/comparative-market-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/comparative-market-analysis/SKILL.md new file mode 100644 index 0000000..6e77a85 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/comparative-market-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a comparative market analysis with structured process, quality checks, and system integration +--- + +# Comparative Market Analysis + +## Purpose + +Analyze and produce a comprehensive comparative market analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing comparative market analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the comparative market analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the comparative market analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Comparative Market Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/construction-budget/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/construction-budget/SKILL.md new file mode 100644 index 0000000..dbf3e86 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/construction-budget/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a construction budget with structured process, quality checks, and system integration +--- + +# Construction Budget + +## Purpose + +Create a comprehensive construction budget that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing construction budget documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the construction budget +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the construction budget using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Construction Budget + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/counter-offer-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/counter-offer-strategy/SKILL.md new file mode 100644 index 0000000..df81c34 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/counter-offer-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a counter offer strategy with structured process, quality checks, and system integration +--- + +# Counter Offer Strategy + +## Purpose + +Design and document a comprehensive counter offer strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing counter offer strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the counter offer strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the counter offer strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Counter Offer Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/depreciation-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/depreciation-analysis/SKILL.md new file mode 100644 index 0000000..9243305 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/depreciation-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a depreciation analysis with structured process, quality checks, and system integration +--- + +# Depreciation Analysis + +## Purpose + +Analyze and produce a comprehensive depreciation analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing depreciation analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the depreciation analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the depreciation analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Depreciation Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/development-feasibility/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/development-feasibility/SKILL.md new file mode 100644 index 0000000..cf8e2f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/development-feasibility/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a development feasibility with structured process, quality checks, and system integration +--- + +# Development Feasibility + +## Purpose + +Create a comprehensive development feasibility that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing development feasibility documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the development feasibility +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the development feasibility using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Development Feasibility + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/exit-strategy-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/exit-strategy-re/SKILL.md new file mode 100644 index 0000000..2391606 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/exit-strategy-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a exit strategy re with structured process, quality checks, and system integration +--- + +# Exit Strategy Re + +## Purpose + +Design and document a comprehensive exit strategy re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing exit strategy re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the exit strategy re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the exit strategy re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Exit Strategy Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/farming-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/farming-strategy/SKILL.md new file mode 100644 index 0000000..1047dfd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/farming-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a farming strategy with structured process, quality checks, and system integration +--- + +# Farming Strategy + +## Purpose + +Design and document a comprehensive farming strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing farming strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the farming strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the farming strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Farming Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/investment-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/investment-analysis/SKILL.md new file mode 100644 index 0000000..ec97a23 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/investment-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a investment analysis with structured process, quality checks, and system integration +--- + +# Investment Analysis + +## Purpose + +Analyze and produce a comprehensive investment analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investment analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investment analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investment analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Investment Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/just-sold-post/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/just-sold-post/SKILL.md new file mode 100644 index 0000000..e24b85a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/just-sold-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a just sold post with structured process, quality checks, and system integration +--- + +# Just Sold Post + +## Purpose + +Create a comprehensive just sold post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing just sold post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the just sold post +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the just sold post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Just Sold Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/lease-agreement-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/lease-agreement-checklist/SKILL.md new file mode 100644 index 0000000..c10b46c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/lease-agreement-checklist/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a lease agreement checklist with structured process, quality checks, and system integration +--- + +# Lease Agreement Checklist + +## Purpose + +Analyze and produce a comprehensive lease agreement checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lease agreement checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lease agreement checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lease agreement checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Lease Agreement Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/listing-description/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/listing-description/SKILL.md new file mode 100644 index 0000000..939ed78 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/listing-description/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a listing description with structured process, quality checks, and system integration +--- + +# Listing Description + +## Purpose + +Create a comprehensive listing description that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing listing description documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the listing description +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the listing description using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Listing Description + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/listing-photography-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/listing-photography-brief/SKILL.md new file mode 100644 index 0000000..702c938 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/listing-photography-brief/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a listing photography brief with structured process, quality checks, and system integration +--- + +# Listing Photography Brief + +## Purpose + +Create a comprehensive listing photography brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing listing photography brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the listing photography brief +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the listing photography brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Listing Photography Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/listing-presentation/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/listing-presentation/SKILL.md new file mode 100644 index 0000000..44e7739 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/listing-presentation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a listing presentation with structured process, quality checks, and system integration +--- + +# Listing Presentation + +## Purpose + +Create a comprehensive listing presentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing listing presentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the listing presentation +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the listing presentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Listing Presentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/maintenance-schedule/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/maintenance-schedule/SKILL.md new file mode 100644 index 0000000..ab5c891 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/maintenance-schedule/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a maintenance schedule with structured process, quality checks, and system integration +--- + +# Maintenance Schedule + +## Purpose + +Design and document a comprehensive maintenance schedule that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing maintenance schedule documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the maintenance schedule +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the maintenance schedule using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Maintenance Schedule + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/market-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/market-analysis/SKILL.md new file mode 100644 index 0000000..0e634f7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/market-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a market analysis with structured process, quality checks, and system integration +--- + +# Market Analysis + +## Purpose + +Analyze and produce a comprehensive market analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Market Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/market-update-newsletter/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/market-update-newsletter/SKILL.md new file mode 100644 index 0000000..eed9fdb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/market-update-newsletter/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a market update newsletter with structured process, quality checks, and system integration +--- + +# Market Update Newsletter + +## Purpose + +Create a comprehensive market update newsletter that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market update newsletter documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market update newsletter +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market update newsletter using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Market Update Newsletter + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/negotiation-script/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/negotiation-script/SKILL.md new file mode 100644 index 0000000..cdc82be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/negotiation-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a negotiation script with structured process, quality checks, and system integration +--- + +# Negotiation Script + +## Purpose + +Create a comprehensive negotiation script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing negotiation script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the negotiation script +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the negotiation script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Negotiation Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/neighborhood-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/neighborhood-analysis/SKILL.md new file mode 100644 index 0000000..bcf590a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/neighborhood-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a neighborhood analysis with structured process, quality checks, and system integration +--- + +# Neighborhood Analysis + +## Purpose + +Analyze and produce a comprehensive neighborhood analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing neighborhood analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the neighborhood analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the neighborhood analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Neighborhood Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/offer-letter-real-estate/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/offer-letter-real-estate/SKILL.md new file mode 100644 index 0000000..004a7b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/offer-letter-real-estate/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a offer letter real estate with structured process, quality checks, and system integration +--- + +# Offer Letter Real Estate + +## Purpose + +Create a comprehensive offer letter real estate that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing offer letter real estate documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the offer letter real estate +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the offer letter real estate using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Offer Letter Real Estate + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/office-lease-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/office-lease-analysis/SKILL.md new file mode 100644 index 0000000..b3fbc82 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/office-lease-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a office lease analysis with structured process, quality checks, and system integration +--- + +# Office Lease Analysis + +## Purpose + +Analyze and produce a comprehensive office lease analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing office lease analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the office lease analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the office lease analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Office Lease Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/open-house-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/open-house-plan/SKILL.md new file mode 100644 index 0000000..ab34ff3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/open-house-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a open house plan with structured process, quality checks, and system integration +--- + +# Open House Plan + +## Purpose + +Design and document a comprehensive open house plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing open house plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the open house plan +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the open house plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Open House Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/portfolio-review/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/portfolio-review/SKILL.md new file mode 100644 index 0000000..8b49160 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/portfolio-review/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a portfolio review with structured process, quality checks, and system integration +--- + +# Portfolio Review + +## Purpose + +Analyze and produce a comprehensive portfolio review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing portfolio review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the portfolio review +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the portfolio review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Portfolio Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/project-timeline-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/project-timeline-re/SKILL.md new file mode 100644 index 0000000..2af0d09 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/project-timeline-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a project timeline re with structured process, quality checks, and system integration +--- + +# Project Timeline Re + +## Purpose + +Create a comprehensive project timeline re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing project timeline re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the project timeline re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the project timeline re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Project Timeline Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/property-inspection/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/property-inspection/SKILL.md new file mode 100644 index 0000000..3540080 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/property-inspection/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a property inspection with structured process, quality checks, and system integration +--- + +# Property Inspection + +## Purpose + +Create a comprehensive property inspection that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing property inspection documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the property inspection +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the property inspection using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Property Inspection + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/property-listing/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/property-listing/SKILL.md new file mode 100644 index 0000000..4fd0dcc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/property-listing/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a property listing with structured process, quality checks, and system integration +--- + +# Property Listing + +## Purpose + +Create a comprehensive property listing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing property listing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the property listing +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the property listing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Property Listing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/property-management-sop/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/property-management-sop/SKILL.md new file mode 100644 index 0000000..b366973 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/property-management-sop/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a property management sop with structured process, quality checks, and system integration +--- + +# Property Management Sop + +## Purpose + +Create a comprehensive property management sop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing property management sop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the property management sop +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the property management sop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Property Management Sop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/real-estate-marketing-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/real-estate-marketing-plan/SKILL.md new file mode 100644 index 0000000..66eecf5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/real-estate-marketing-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a real estate marketing plan with structured process, quality checks, and system integration +--- + +# Real Estate Marketing Plan + +## Purpose + +Design and document a comprehensive real estate marketing plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing real estate marketing plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the real estate marketing plan +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the real estate marketing plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Real Estate Marketing Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/referral-program-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/referral-program-re/SKILL.md new file mode 100644 index 0000000..fbb0156 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/referral-program-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a referral program re with structured process, quality checks, and system integration +--- + +# Referral Program Re + +## Purpose + +Design and document a comprehensive referral program re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral program re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral program re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral program re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Referral Program Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/rental-property-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/rental-property-analysis/SKILL.md new file mode 100644 index 0000000..7e95a74 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/rental-property-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a rental property analysis with structured process, quality checks, and system integration +--- + +# Rental Property Analysis + +## Purpose + +Analyze and produce a comprehensive rental property analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rental property analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rental property analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rental property analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Rental Property Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/retail-space-evaluation/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/retail-space-evaluation/SKILL.md new file mode 100644 index 0000000..636d4d3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/retail-space-evaluation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a retail space evaluation with structured process, quality checks, and system integration +--- + +# Retail Space Evaluation + +## Purpose + +Analyze and produce a comprehensive retail space evaluation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retail space evaluation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retail space evaluation +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retail space evaluation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Retail Space Evaluation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/seller-consultation/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/seller-consultation/SKILL.md new file mode 100644 index 0000000..d1b468f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/seller-consultation/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a seller consultation with structured process, quality checks, and system integration +--- + +# Seller Consultation + +## Purpose + +Create a comprehensive seller consultation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seller consultation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seller consultation +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seller consultation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Seller Consultation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/showing-feedback/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/showing-feedback/SKILL.md new file mode 100644 index 0000000..ccfe620 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/showing-feedback/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a showing feedback with structured process, quality checks, and system integration +--- + +# Showing Feedback + +## Purpose + +Create a comprehensive showing feedback that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing showing feedback documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the showing feedback +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the showing feedback using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Showing Feedback + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/sphere-of-influence/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/sphere-of-influence/SKILL.md new file mode 100644 index 0000000..687065a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/sphere-of-influence/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a sphere of influence with structured process, quality checks, and system integration +--- + +# Sphere Of Influence + +## Purpose + +Create a comprehensive sphere of influence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sphere of influence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sphere of influence +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sphere of influence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Sphere Of Influence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/tax-strategy-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/tax-strategy-re/SKILL.md new file mode 100644 index 0000000..cf2fff8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/tax-strategy-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a tax strategy re with structured process, quality checks, and system integration +--- + +# Tax Strategy Re + +## Purpose + +Design and document a comprehensive tax strategy re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tax strategy re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tax strategy re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tax strategy re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Tax Strategy Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/tenant-screening/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/tenant-screening/SKILL.md new file mode 100644 index 0000000..458d8f6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/tenant-screening/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a tenant screening with structured process, quality checks, and system integration +--- + +# Tenant Screening + +## Purpose + +Create a comprehensive tenant screening that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tenant screening documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tenant screening +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tenant screening using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Tenant Screening + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/vacation-rental-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/vacation-rental-strategy/SKILL.md new file mode 100644 index 0000000..f3802ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/vacation-rental-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a vacation rental strategy with structured process, quality checks, and system integration +--- + +# Vacation Rental Strategy + +## Purpose + +Design and document a comprehensive vacation rental strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vacation rental strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vacation rental strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vacation rental strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Vacation Rental Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/real-estate/vendor-management-re/SKILL.md b/clowdex-download/.claude/.claude/skills/real-estate/vendor-management-re/SKILL.md new file mode 100644 index 0000000..bb4e406 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/real-estate/vendor-management-re/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a vendor management re with structured process, quality checks, and system integration +--- + +# Vendor Management Re + +## Purpose + +Create a comprehensive vendor management re that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Real Estate + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor management re documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Comparable Market Analysis, Cap Rate Analysis, Cash-on-Cash Return + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor management re +- Identify gaps, opportunities, and risks +- Define success metrics: Days on Market, List-to-Sale Ratio, Cap Rate, Cash-on-Cash Return +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor management re using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Price based on comparables within 0.5 miles and 6 months + +## Output Format + +```markdown +# Vendor Management Re + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Comparable Market Analysis +- Cap Rate Analysis +- Cash-on-Cash Return +- Gross Rent Multiplier +- BRRRR Strategy +- 1031 Exchange + +## Key Metrics +- Days on Market +- List-to-Sale Ratio +- Cap Rate +- Cash-on-Cash Return +- Occupancy Rate +- Net Operating Income +- Price Per Square Foot + +## Best Practices +- Price based on comparables within 0.5 miles and 6 months +- Professional photos increase views 118% +- Respond to inquiries within 5 minutes +- Stage homes before listing +- Inspect before making offers + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/account-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/account-plan/SKILL.md new file mode 100644 index 0000000..9f00352 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/account-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a account plan with structured process, quality checks, and system integration +--- + +# Account Plan + +## Purpose + +Design and document a comprehensive account plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing account plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the account plan +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the account plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Account Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/affiliate-program/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/affiliate-program/SKILL.md new file mode 100644 index 0000000..a509842 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/affiliate-program/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a affiliate program with structured process, quality checks, and system integration +--- + +# Affiliate Program + +## Purpose + +Design and document a comprehensive affiliate program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing affiliate program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the affiliate program +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the affiliate program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Affiliate Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/boardroom-presentation/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/boardroom-presentation/SKILL.md new file mode 100644 index 0000000..430d0d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/boardroom-presentation/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a boardroom presentation with structured process, quality checks, and system integration +--- + +# Boardroom Presentation + +## Purpose + +Create a comprehensive boardroom presentation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing boardroom presentation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the boardroom presentation +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the boardroom presentation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Boardroom Presentation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/breakup-email/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/breakup-email/SKILL.md new file mode 100644 index 0000000..f9fa0cb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/breakup-email/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a breakup email with structured process, quality checks, and system integration +--- + +# Breakup Email + +## Purpose + +Create a comprehensive breakup email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing breakup email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the breakup email +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the breakup email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Breakup Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/business-case/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/business-case/SKILL.md new file mode 100644 index 0000000..3e8ddcf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/business-case/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a business case with structured process, quality checks, and system integration +--- + +# Business Case + +## Purpose + +Create a comprehensive business case that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business case documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business case +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business case using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Business Case + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/buyer-persona-sales/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/buyer-persona-sales/SKILL.md new file mode 100644 index 0000000..dc7bf27 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/buyer-persona-sales/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a buyer persona sales with structured process, quality checks, and system integration +--- + +# Buyer Persona Sales + +## Purpose + +Create a comprehensive buyer persona sales that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing buyer persona sales documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the buyer persona sales +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the buyer persona sales using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Buyer Persona Sales + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/cadence-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/cadence-optimization/SKILL.md new file mode 100644 index 0000000..6de5cdf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/cadence-optimization/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a cadence optimization with structured process, quality checks, and system integration +--- + +# Cadence Optimization + +## Purpose + +Create a comprehensive cadence optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cadence optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cadence optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cadence optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Cadence Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/case-study-sales/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/case-study-sales/SKILL.md new file mode 100644 index 0000000..e5d50a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/case-study-sales/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a case study sales with structured process, quality checks, and system integration +--- + +# Case Study Sales + +## Purpose + +Create a comprehensive case study sales that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing case study sales documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the case study sales +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the case study sales using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Case Study Sales + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/channel-partner-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/channel-partner-strategy/SKILL.md new file mode 100644 index 0000000..4ee7539 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/channel-partner-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a channel partner strategy with structured process, quality checks, and system integration +--- + +# Channel Partner Strategy + +## Purpose + +Design and document a comprehensive channel partner strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing channel partner strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the channel partner strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the channel partner strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Channel Partner Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/churn-prevention/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/churn-prevention/SKILL.md new file mode 100644 index 0000000..af24850 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/churn-prevention/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a churn prevention with structured process, quality checks, and system integration +--- + +# Churn Prevention + +## Purpose + +Create a comprehensive churn prevention that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing churn prevention documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the churn prevention +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the churn prevention using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Churn Prevention + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/cold-call-script/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/cold-call-script/SKILL.md new file mode 100644 index 0000000..7ad9b1b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/cold-call-script/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a cold call script with structured process, quality checks, and system integration +--- + +# Cold Call Script + +## Purpose + +Create a comprehensive cold call script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cold call script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cold call script +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cold call script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Cold Call Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/cold-email/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/cold-email/SKILL.md new file mode 100644 index 0000000..b4189fc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/cold-email/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a cold email with structured process, quality checks, and system integration +--- + +# Cold Email + +## Purpose + +Create a comprehensive cold email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cold email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cold email +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cold email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Cold Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/cold-linkedin-message/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/cold-linkedin-message/SKILL.md new file mode 100644 index 0000000..802a89c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/cold-linkedin-message/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a cold linkedin message with structured process, quality checks, and system integration +--- + +# Cold Linkedin Message + +## Purpose + +Create a comprehensive cold linkedin message that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cold linkedin message documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cold linkedin message +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cold linkedin message using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Cold Linkedin Message + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/commission-structure/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/commission-structure/SKILL.md new file mode 100644 index 0000000..b440988 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/commission-structure/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a commission structure with structured process, quality checks, and system integration +--- + +# Commission Structure + +## Purpose + +Create a comprehensive commission structure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing commission structure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the commission structure +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the commission structure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Commission Structure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/competitor-battlecard/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/competitor-battlecard/SKILL.md new file mode 100644 index 0000000..097e5e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/competitor-battlecard/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a competitor battlecard with structured process, quality checks, and system integration +--- + +# Competitor Battlecard + +## Purpose + +Create a comprehensive competitor battlecard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitor battlecard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitor battlecard +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitor battlecard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Competitor Battlecard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/crm-setup-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/crm-setup-guide/SKILL.md new file mode 100644 index 0000000..a37a8b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/crm-setup-guide/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a crm setup guide with structured process, quality checks, and system integration +--- + +# Crm Setup Guide + +## Purpose + +Design and document a comprehensive crm setup guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crm setup guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crm setup guide +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crm setup guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Crm Setup Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/cross-sell-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/cross-sell-playbook/SKILL.md new file mode 100644 index 0000000..225e3f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/cross-sell-playbook/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a cross sell playbook with structured process, quality checks, and system integration +--- + +# Cross Sell Playbook + +## Purpose + +Design and document a comprehensive cross sell playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross sell playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross sell playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross sell playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Cross Sell Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/deal-qualification/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/deal-qualification/SKILL.md new file mode 100644 index 0000000..b364f95 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/deal-qualification/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a deal qualification with structured process, quality checks, and system integration +--- + +# Deal Qualification + +## Purpose + +Create a comprehensive deal qualification that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deal qualification documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deal qualification +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deal qualification using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Deal Qualification + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/deal-scoring/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/deal-scoring/SKILL.md new file mode 100644 index 0000000..5e1d5c9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/deal-scoring/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a deal scoring with structured process, quality checks, and system integration +--- + +# Deal Scoring + +## Purpose + +Analyze and produce a comprehensive deal scoring that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing deal scoring documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the deal scoring +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the deal scoring using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Deal Scoring + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/demo-script/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/demo-script/SKILL.md new file mode 100644 index 0000000..66e70d5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/demo-script/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a demo script with structured process, quality checks, and system integration +--- + +# Demo Script + +## Purpose + +Create a comprehensive demo script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing demo script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the demo script +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the demo script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Demo Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/discovery-call-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/discovery-call-guide/SKILL.md new file mode 100644 index 0000000..b264d2c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/discovery-call-guide/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a discovery call guide with structured process, quality checks, and system integration +--- + +# Discovery Call Guide + +## Purpose + +Design and document a comprehensive discovery call guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing discovery call guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the discovery call guide +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the discovery call guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Discovery Call Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/executive-sponsor-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/executive-sponsor-plan/SKILL.md new file mode 100644 index 0000000..16d2922 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/executive-sponsor-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a executive sponsor plan with structured process, quality checks, and system integration +--- + +# Executive Sponsor Plan + +## Purpose + +Design and document a comprehensive executive sponsor plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive sponsor plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive sponsor plan +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive sponsor plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Executive Sponsor Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/expansion-revenue-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/expansion-revenue-plan/SKILL.md new file mode 100644 index 0000000..7ae7d4f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/expansion-revenue-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a expansion revenue plan with structured process, quality checks, and system integration +--- + +# Expansion Revenue Plan + +## Purpose + +Design and document a comprehensive expansion revenue plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing expansion revenue plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the expansion revenue plan +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the expansion revenue plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Expansion Revenue Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/follow-up-email/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/follow-up-email/SKILL.md new file mode 100644 index 0000000..9fde226 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/follow-up-email/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a follow up email with structured process, quality checks, and system integration +--- + +# Follow Up Email + +## Purpose + +Create a comprehensive follow up email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing follow up email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the follow up email +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the follow up email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Follow Up Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/forecast-model/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/forecast-model/SKILL.md new file mode 100644 index 0000000..140e142 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/forecast-model/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a forecast model with structured process, quality checks, and system integration +--- + +# Forecast Model + +## Purpose + +Analyze and produce a comprehensive forecast model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing forecast model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the forecast model +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the forecast model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Forecast Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/ideal-customer-profile/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/ideal-customer-profile/SKILL.md new file mode 100644 index 0000000..28941ce --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/ideal-customer-profile/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a ideal customer profile with structured process, quality checks, and system integration +--- + +# Ideal Customer Profile + +## Purpose + +Create a comprehensive ideal customer profile that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ideal customer profile documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ideal customer profile +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ideal customer profile using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Ideal Customer Profile + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/incentive-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/incentive-plan/SKILL.md new file mode 100644 index 0000000..7b30c71 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/incentive-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a incentive plan with structured process, quality checks, and system integration +--- + +# Incentive Plan + +## Purpose + +Design and document a comprehensive incentive plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incentive plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incentive plan +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incentive plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Incentive Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/lead-scoring-model/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/lead-scoring-model/SKILL.md new file mode 100644 index 0000000..a850175 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/lead-scoring-model/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a lead scoring model with structured process, quality checks, and system integration +--- + +# Lead Scoring Model + +## Purpose + +Analyze and produce a comprehensive lead scoring model that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lead scoring model documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lead scoring model +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lead scoring model using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Lead Scoring Model + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/objection-handling/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/objection-handling/SKILL.md new file mode 100644 index 0000000..0caeb68 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/objection-handling/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a objection handling with structured process, quality checks, and system integration +--- + +# Objection Handling + +## Purpose + +Create a comprehensive objection handling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing objection handling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the objection handling +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the objection handling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Objection Handling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/onboarding-sales-rep/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/onboarding-sales-rep/SKILL.md new file mode 100644 index 0000000..ca95855 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/onboarding-sales-rep/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a onboarding sales rep with structured process, quality checks, and system integration +--- + +# Onboarding Sales Rep + +## Purpose + +Create a comprehensive onboarding sales rep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing onboarding sales rep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the onboarding sales rep +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the onboarding sales rep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Onboarding Sales Rep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/one-pager/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/one-pager/SKILL.md new file mode 100644 index 0000000..2d408d2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/one-pager/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a one pager with structured process, quality checks, and system integration +--- + +# One Pager + +## Purpose + +Create a comprehensive one pager that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing one pager documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the one pager +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the one pager using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# One Pager + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/pipeline-review/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/pipeline-review/SKILL.md new file mode 100644 index 0000000..dea7332 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/pipeline-review/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a pipeline review with structured process, quality checks, and system integration +--- + +# Pipeline Review + +## Purpose + +Analyze and produce a comprehensive pipeline review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pipeline review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pipeline review +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pipeline review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Pipeline Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/pipeline-stage-definitions/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/pipeline-stage-definitions/SKILL.md new file mode 100644 index 0000000..1f1d459 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/pipeline-stage-definitions/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a pipeline stage definitions with structured process, quality checks, and system integration +--- + +# Pipeline Stage Definitions + +## Purpose + +Design and document a comprehensive pipeline stage definitions that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pipeline stage definitions documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pipeline stage definitions +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pipeline stage definitions using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Pipeline Stage Definitions + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/pricing-negotiation/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/pricing-negotiation/SKILL.md new file mode 100644 index 0000000..afa7c5b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/pricing-negotiation/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a pricing negotiation with structured process, quality checks, and system integration +--- + +# Pricing Negotiation + +## Purpose + +Create a comprehensive pricing negotiation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing negotiation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing negotiation +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing negotiation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Pricing Negotiation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/procurement-response/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/procurement-response/SKILL.md new file mode 100644 index 0000000..d1c6d05 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/procurement-response/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a procurement response with structured process, quality checks, and system integration +--- + +# Procurement Response + +## Purpose + +Create a comprehensive procurement response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing procurement response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the procurement response +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the procurement response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Procurement Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/proposal-writer/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/proposal-writer/SKILL.md new file mode 100644 index 0000000..a245839 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/proposal-writer/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a proposal writer with structured process, quality checks, and system integration +--- + +# Proposal Writer + +## Purpose + +Create a comprehensive proposal writer that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing proposal writer documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the proposal writer +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the proposal writer using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Proposal Writer + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/quarterly-business-review/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/quarterly-business-review/SKILL.md new file mode 100644 index 0000000..ac9da99 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/quarterly-business-review/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a quarterly business review with structured process, quality checks, and system integration +--- + +# Quarterly Business Review + +## Purpose + +Analyze and produce a comprehensive quarterly business review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quarterly business review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quarterly business review +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quarterly business review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Quarterly Business Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/quota-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/quota-planning/SKILL.md new file mode 100644 index 0000000..c284ff6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/quota-planning/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a quota planning with structured process, quality checks, and system integration +--- + +# Quota Planning + +## Purpose + +Design and document a comprehensive quota planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing quota planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the quota planning +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the quota planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Quota Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/re-engagement-email/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/re-engagement-email/SKILL.md new file mode 100644 index 0000000..2bb17f9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/re-engagement-email/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a re engagement email with structured process, quality checks, and system integration +--- + +# Re Engagement Email + +## Purpose + +Create a comprehensive re engagement email that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing re engagement email documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the re engagement email +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the re engagement email using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Re Engagement Email + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/referral-ask/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/referral-ask/SKILL.md new file mode 100644 index 0000000..6324443 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/referral-ask/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a referral ask with structured process, quality checks, and system integration +--- + +# Referral Ask + +## Purpose + +Create a comprehensive referral ask that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing referral ask documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the referral ask +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the referral ask using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Referral Ask + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/renewal-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/renewal-strategy/SKILL.md new file mode 100644 index 0000000..7bd1c9a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/renewal-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a renewal strategy with structured process, quality checks, and system integration +--- + +# Renewal Strategy + +## Purpose + +Design and document a comprehensive renewal strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing renewal strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the renewal strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the renewal strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Renewal Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/reseller-program/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/reseller-program/SKILL.md new file mode 100644 index 0000000..76d97a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/reseller-program/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a reseller program with structured process, quality checks, and system integration +--- + +# Reseller Program + +## Purpose + +Design and document a comprehensive reseller program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reseller program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reseller program +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reseller program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Reseller Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/rfp-response-sales/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/rfp-response-sales/SKILL.md new file mode 100644 index 0000000..67ef8a2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/rfp-response-sales/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a rfp response sales with structured process, quality checks, and system integration +--- + +# Rfp Response Sales + +## Purpose + +Create a comprehensive rfp response sales that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing rfp response sales documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the rfp response sales +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the rfp response sales using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Rfp Response Sales + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/roi-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/roi-calculator/SKILL.md new file mode 100644 index 0000000..cfd039e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/roi-calculator/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a roi calculator with structured process, quality checks, and system integration +--- + +# Roi Calculator + +## Purpose + +Create a comprehensive roi calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing roi calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the roi calculator +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the roi calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Roi Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/role-play-scenario/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/role-play-scenario/SKILL.md new file mode 100644 index 0000000..63c6106 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/role-play-scenario/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a role play scenario with structured process, quality checks, and system integration +--- + +# Role Play Scenario + +## Purpose + +Create a comprehensive role play scenario that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing role play scenario documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the role play scenario +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the role play scenario using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Role Play Scenario + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-automation/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-automation/SKILL.md new file mode 100644 index 0000000..1e4f771 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-automation/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales automation with structured process, quality checks, and system integration +--- + +# Sales Automation + +## Purpose + +Create a comprehensive sales automation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales automation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales automation +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales automation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Automation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-contract/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-contract/SKILL.md new file mode 100644 index 0000000..1ff39ef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-contract/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales contract with structured process, quality checks, and system integration +--- + +# Sales Contract + +## Purpose + +Create a comprehensive sales contract that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales contract documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales contract +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales contract using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Contract + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-dashboard/SKILL.md new file mode 100644 index 0000000..e9a41ed --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-dashboard/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a sales dashboard with structured process, quality checks, and system integration +--- + +# Sales Dashboard + +## Purpose + +Analyze and produce a comprehensive sales dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-enablement-content/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-enablement-content/SKILL.md new file mode 100644 index 0000000..b26ff6d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-enablement-content/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales enablement content with structured process, quality checks, and system integration +--- + +# Sales Enablement Content + +## Purpose + +Create a comprehensive sales enablement content that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales enablement content documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales enablement content +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales enablement content using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Enablement Content + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-kpi-tracker/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-kpi-tracker/SKILL.md new file mode 100644 index 0000000..ad88336 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-kpi-tracker/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a sales kpi tracker with structured process, quality checks, and system integration +--- + +# Sales Kpi Tracker + +## Purpose + +Analyze and produce a comprehensive sales kpi tracker that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales kpi tracker documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales kpi tracker +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales kpi tracker using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Kpi Tracker + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-meeting-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-meeting-prep/SKILL.md new file mode 100644 index 0000000..3e7c59d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-meeting-prep/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales meeting prep with structured process, quality checks, and system integration +--- + +# Sales Meeting Prep + +## Purpose + +Create a comprehensive sales meeting prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales meeting prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales meeting prep +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales meeting prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Meeting Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-pitch/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-pitch/SKILL.md new file mode 100644 index 0000000..5353165 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-pitch/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales pitch with structured process, quality checks, and system integration +--- + +# Sales Pitch + +## Purpose + +Create a comprehensive sales pitch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales pitch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales pitch +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales pitch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Pitch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-playbook/SKILL.md new file mode 100644 index 0000000..bde8e00 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-playbook/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a sales playbook with structured process, quality checks, and system integration +--- + +# Sales Playbook + +## Purpose + +Design and document a comprehensive sales playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-process-design/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-process-design/SKILL.md new file mode 100644 index 0000000..c852070 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-process-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sales process design with structured process, quality checks, and system integration +--- + +# Sales Process Design + +## Purpose + +Create a comprehensive sales process design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales process design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales process design +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales process design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Process Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-strategy/SKILL.md new file mode 100644 index 0000000..bf12e4e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a sales strategy with structured process, quality checks, and system integration +--- + +# Sales Strategy + +## Purpose + +Design and document a comprehensive sales strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sales-training-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sales-training-plan/SKILL.md new file mode 100644 index 0000000..d84d5c1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sales-training-plan/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a sales training plan with structured process, quality checks, and system integration +--- + +# Sales Training Plan + +## Purpose + +Design and document a comprehensive sales training plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sales training plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sales training plan +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sales training plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sales Training Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sell-sheet/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sell-sheet/SKILL.md new file mode 100644 index 0000000..22acc3e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sell-sheet/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sell sheet with structured process, quality checks, and system integration +--- + +# Sell Sheet + +## Purpose + +Create a comprehensive sell sheet that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sell sheet documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sell sheet +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sell sheet using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sell Sheet + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/sequence-design/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/sequence-design/SKILL.md new file mode 100644 index 0000000..c2b8a87 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/sequence-design/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a sequence design with structured process, quality checks, and system integration +--- + +# Sequence Design + +## Purpose + +Create a comprehensive sequence design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sequence design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sequence design +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sequence design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Sequence Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/spiff-program/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/spiff-program/SKILL.md new file mode 100644 index 0000000..bba004e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/spiff-program/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a spiff program with structured process, quality checks, and system integration +--- + +# Spiff Program + +## Purpose + +Design and document a comprehensive spiff program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing spiff program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the spiff program +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the spiff program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Spiff Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/statement-of-work/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/statement-of-work/SKILL.md new file mode 100644 index 0000000..e83ef1d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/statement-of-work/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a statement of work with structured process, quality checks, and system integration +--- + +# Statement Of Work + +## Purpose + +Create a comprehensive statement of work that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing statement of work documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the statement of work +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the statement of work using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Statement Of Work + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/strategic-account-review/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/strategic-account-review/SKILL.md new file mode 100644 index 0000000..7ae90fb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/strategic-account-review/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a strategic account review with structured process, quality checks, and system integration +--- + +# Strategic Account Review + +## Purpose + +Analyze and produce a comprehensive strategic account review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing strategic account review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the strategic account review +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the strategic account review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Strategic Account Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/target-account-list/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/target-account-list/SKILL.md new file mode 100644 index 0000000..08534e3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/target-account-list/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a target account list with structured process, quality checks, and system integration +--- + +# Target Account List + +## Purpose + +Create a comprehensive target account list that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing target account list documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the target account list +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the target account list using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Target Account List + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/territory-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/territory-planning/SKILL.md new file mode 100644 index 0000000..bcf1412 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/territory-planning/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a territory planning with structured process, quality checks, and system integration +--- + +# Territory Planning + +## Purpose + +Design and document a comprehensive territory planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing territory planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the territory planning +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the territory planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Territory Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/upsell-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/upsell-strategy/SKILL.md new file mode 100644 index 0000000..d3fb4cb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/upsell-strategy/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Design and document a upsell strategy with structured process, quality checks, and system integration +--- + +# Upsell Strategy + +## Purpose + +Design and document a comprehensive upsell strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing upsell strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the upsell strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the upsell strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Upsell Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/vendor-questionnaire/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/vendor-questionnaire/SKILL.md new file mode 100644 index 0000000..17169cb --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/vendor-questionnaire/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Create a vendor questionnaire with structured process, quality checks, and system integration +--- + +# Vendor Questionnaire + +## Purpose + +Create a comprehensive vendor questionnaire that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing vendor questionnaire documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the vendor questionnaire +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the vendor questionnaire using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Vendor Questionnaire + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/sales/win-loss-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/sales/win-loss-analysis/SKILL.md new file mode 100644 index 0000000..4e427a6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/sales/win-loss-analysis/SKILL.md @@ -0,0 +1,134 @@ +--- +description: Analyze and produce a win loss analysis with structured process, quality checks, and system integration +--- + +# Win Loss Analysis + +## Purpose + +Analyze and produce a comprehensive win loss analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Sales & Revenue + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Customer**: ICP or specific prospect details + +### Optional +- **Product/Service**: What you're selling and key differentiators +- **Stage**: Where the prospect is in the buying journey + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing win loss analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: BANT (Budget, Authority, Need, Timeline), MEDDIC, Challenger Sale + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the win loss analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Win Rate, Average Deal Size, Sales Cycle Length, Pipeline Velocity +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the win loss analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Qualify early and disqualify fast + +## Output Format + +```markdown +# Win Loss Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- BANT (Budget, Authority, Need, Timeline) +- MEDDIC +- Challenger Sale +- SPIN Selling +- Sandler Selling System +- Solution Selling +- Value Selling + +## Key Metrics +- Win Rate +- Average Deal Size +- Sales Cycle Length +- Pipeline Velocity +- Quota Attainment +- Activity Metrics (calls/emails/meetings) +- Forecast Accuracy + +## Best Practices +- Qualify early and disqualify fast +- Follow up within 5 minutes of inbound leads +- Multi-thread every deal (3+ contacts) +- Always confirm next steps before ending a call +- Log every interaction in CRM within 24 hours + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/app-store-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/app-store-optimization/SKILL.md new file mode 100644 index 0000000..f07fb13 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/app-store-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a app store optimization with structured process, quality checks, and system integration +--- + +# App Store Optimization + +## Purpose + +Create a comprehensive app store optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing app store optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the app store optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the app store optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# App Store Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/backlink-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/backlink-audit/SKILL.md new file mode 100644 index 0000000..146aa93 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/backlink-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a backlink audit with structured process, quality checks, and system integration +--- + +# Backlink Audit + +## Purpose + +Analyze and produce a comprehensive backlink audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing backlink audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the backlink audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the backlink audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Backlink Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/broken-link-building/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/broken-link-building/SKILL.md new file mode 100644 index 0000000..5fb24d7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/broken-link-building/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a broken link building with structured process, quality checks, and system integration +--- + +# Broken Link Building + +## Purpose + +Create a comprehensive broken link building that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing broken link building documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the broken link building +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the broken link building using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Broken Link Building + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/canonical-tag-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/canonical-tag-strategy/SKILL.md new file mode 100644 index 0000000..dd7c3c8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/canonical-tag-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a canonical tag strategy with structured process, quality checks, and system integration +--- + +# Canonical Tag Strategy + +## Purpose + +Design and document a comprehensive canonical tag strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing canonical tag strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the canonical tag strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the canonical tag strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Canonical Tag Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/category-page-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/category-page-optimization/SKILL.md new file mode 100644 index 0000000..b83447f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/category-page-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a category page optimization with structured process, quality checks, and system integration +--- + +# Category Page Optimization + +## Purpose + +Create a comprehensive category page optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing category page optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the category page optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the category page optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Category Page Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/competitor-seo-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/competitor-seo-analysis/SKILL.md new file mode 100644 index 0000000..071dc13 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/competitor-seo-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a competitor seo analysis with structured process, quality checks, and system integration +--- + +# Competitor Seo Analysis + +## Purpose + +Analyze and produce a comprehensive competitor seo analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitor seo analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitor seo analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitor seo analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Competitor Seo Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/content-decay-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/content-decay-analysis/SKILL.md new file mode 100644 index 0000000..316d913 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/content-decay-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a content decay analysis with structured process, quality checks, and system integration +--- + +# Content Decay Analysis + +## Purpose + +Analyze and produce a comprehensive content decay analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content decay analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content decay analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content decay analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Content Decay Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/content-refresh-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/content-refresh-plan/SKILL.md new file mode 100644 index 0000000..f77b820 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/content-refresh-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a content refresh plan with structured process, quality checks, and system integration +--- + +# Content Refresh Plan + +## Purpose + +Design and document a comprehensive content refresh plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content refresh plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content refresh plan +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content refresh plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Content Refresh Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/content-seo-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/content-seo-brief/SKILL.md new file mode 100644 index 0000000..889ceea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/content-seo-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a content seo brief with structured process, quality checks, and system integration +--- + +# Content Seo Brief + +## Purpose + +Create a comprehensive content seo brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing content seo brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the content seo brief +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the content seo brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Content Seo Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/conversion-tracking-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/conversion-tracking-setup/SKILL.md new file mode 100644 index 0000000..096a907 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/conversion-tracking-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a conversion tracking setup with structured process, quality checks, and system integration +--- + +# Conversion Tracking Setup + +## Purpose + +Design and document a comprehensive conversion tracking setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conversion tracking setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conversion tracking setup +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conversion tracking setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Conversion Tracking Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/core-web-vitals-fix/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/core-web-vitals-fix/SKILL.md new file mode 100644 index 0000000..8c57846 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/core-web-vitals-fix/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a core web vitals fix with structured process, quality checks, and system integration +--- + +# Core Web Vitals Fix + +## Purpose + +Create a comprehensive core web vitals fix that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing core web vitals fix documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the core web vitals fix +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the core web vitals fix using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Core Web Vitals Fix + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/crawl-budget-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/crawl-budget-optimization/SKILL.md new file mode 100644 index 0000000..8f90c7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/crawl-budget-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a crawl budget optimization with structured process, quality checks, and system integration +--- + +# Crawl Budget Optimization + +## Purpose + +Create a comprehensive crawl budget optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crawl budget optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crawl budget optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crawl budget optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Crawl Budget Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/digital-pr-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/digital-pr-plan/SKILL.md new file mode 100644 index 0000000..120c0a8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/digital-pr-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a digital pr plan with structured process, quality checks, and system integration +--- + +# Digital Pr Plan + +## Purpose + +Design and document a comprehensive digital pr plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing digital pr plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the digital pr plan +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the digital pr plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Digital Pr Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/ecommerce-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/ecommerce-seo/SKILL.md new file mode 100644 index 0000000..6b355f0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/ecommerce-seo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ecommerce seo with structured process, quality checks, and system integration +--- + +# Ecommerce Seo + +## Purpose + +Create a comprehensive ecommerce seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ecommerce seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ecommerce seo +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ecommerce seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Ecommerce Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/featured-snippet-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/featured-snippet-optimization/SKILL.md new file mode 100644 index 0000000..7f299b1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/featured-snippet-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a featured snippet optimization with structured process, quality checks, and system integration +--- + +# Featured Snippet Optimization + +## Purpose + +Create a comprehensive featured snippet optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing featured snippet optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the featured snippet optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the featured snippet optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Featured Snippet Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/google-analytics-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/google-analytics-setup/SKILL.md new file mode 100644 index 0000000..81b6391 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/google-analytics-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a google analytics setup with structured process, quality checks, and system integration +--- + +# Google Analytics Setup + +## Purpose + +Design and document a comprehensive google analytics setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing google analytics setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the google analytics setup +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the google analytics setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Google Analytics Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/google-business-profile/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/google-business-profile/SKILL.md new file mode 100644 index 0000000..52be498 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/google-business-profile/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a google business profile with structured process, quality checks, and system integration +--- + +# Google Business Profile + +## Purpose + +Create a comprehensive google business profile that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing google business profile documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the google business profile +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the google business profile using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Google Business Profile + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/google-search-console-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/google-search-console-audit/SKILL.md new file mode 100644 index 0000000..fc15da2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/google-search-console-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a google search console audit with structured process, quality checks, and system integration +--- + +# Google Search Console Audit + +## Purpose + +Analyze and produce a comprehensive google search console audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing google search console audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the google search console audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the google search console audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Google Search Console Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/guest-post-outreach/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/guest-post-outreach/SKILL.md new file mode 100644 index 0000000..a9550ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/guest-post-outreach/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a guest post outreach with structured process, quality checks, and system integration +--- + +# Guest Post Outreach + +## Purpose + +Create a comprehensive guest post outreach that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing guest post outreach documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the guest post outreach +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the guest post outreach using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Guest Post Outreach + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/haro-response/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/haro-response/SKILL.md new file mode 100644 index 0000000..4b21ed8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/haro-response/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a haro response with structured process, quality checks, and system integration +--- + +# Haro Response + +## Purpose + +Create a comprehensive haro response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing haro response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the haro response +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the haro response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Haro Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/header-tag-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/header-tag-optimization/SKILL.md new file mode 100644 index 0000000..cb015a7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/header-tag-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a header tag optimization with structured process, quality checks, and system integration +--- + +# Header Tag Optimization + +## Purpose + +Create a comprehensive header tag optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing header tag optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the header tag optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the header tag optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Header Tag Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/hreflang-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/hreflang-setup/SKILL.md new file mode 100644 index 0000000..e460601 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/hreflang-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a hreflang setup with structured process, quality checks, and system integration +--- + +# Hreflang Setup + +## Purpose + +Design and document a comprehensive hreflang setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hreflang setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hreflang setup +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hreflang setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Hreflang Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/image-alt-text-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/image-alt-text-optimization/SKILL.md new file mode 100644 index 0000000..8f7d8e7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/image-alt-text-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a image alt text optimization with structured process, quality checks, and system integration +--- + +# Image Alt Text Optimization + +## Purpose + +Create a comprehensive image alt text optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing image alt text optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the image alt text optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the image alt text optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Image Alt Text Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/internal-linking-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/internal-linking-strategy/SKILL.md new file mode 100644 index 0000000..7beae18 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/internal-linking-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a internal linking strategy with structured process, quality checks, and system integration +--- + +# Internal Linking Strategy + +## Purpose + +Design and document a comprehensive internal linking strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing internal linking strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the internal linking strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the internal linking strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Internal Linking Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/international-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/international-seo/SKILL.md new file mode 100644 index 0000000..6f0bb15 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/international-seo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a international seo with structured process, quality checks, and system integration +--- + +# International Seo + +## Purpose + +Create a comprehensive international seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing international seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the international seo +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the international seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# International Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/keyword-clustering/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/keyword-clustering/SKILL.md new file mode 100644 index 0000000..1b1dfdc --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/keyword-clustering/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a keyword clustering with structured process, quality checks, and system integration +--- + +# Keyword Clustering + +## Purpose + +Create a comprehensive keyword clustering that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing keyword clustering documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the keyword clustering +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the keyword clustering using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Keyword Clustering + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/keyword-gap-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/keyword-gap-analysis/SKILL.md new file mode 100644 index 0000000..cb69cf9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/keyword-gap-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a keyword gap analysis with structured process, quality checks, and system integration +--- + +# Keyword Gap Analysis + +## Purpose + +Analyze and produce a comprehensive keyword gap analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing keyword gap analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the keyword gap analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the keyword gap analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Keyword Gap Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/keyword-research/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/keyword-research/SKILL.md new file mode 100644 index 0000000..5753f3b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/keyword-research/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a keyword research with structured process, quality checks, and system integration +--- + +# Keyword Research + +## Purpose + +Create a comprehensive keyword research that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing keyword research documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the keyword research +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the keyword research using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Keyword Research + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/link-building-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/link-building-strategy/SKILL.md new file mode 100644 index 0000000..b6e1e7a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/link-building-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a link building strategy with structured process, quality checks, and system integration +--- + +# Link Building Strategy + +## Purpose + +Design and document a comprehensive link building strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing link building strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the link building strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the link building strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Link Building Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/local-citation-building/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/local-citation-building/SKILL.md new file mode 100644 index 0000000..f0962db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/local-citation-building/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a local citation building with structured process, quality checks, and system integration +--- + +# Local Citation Building + +## Purpose + +Create a comprehensive local citation building that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local citation building documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local citation building +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local citation building using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Local Citation Building + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/local-keyword-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/local-keyword-strategy/SKILL.md new file mode 100644 index 0000000..817a4ed --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/local-keyword-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a local keyword strategy with structured process, quality checks, and system integration +--- + +# Local Keyword Strategy + +## Purpose + +Design and document a comprehensive local keyword strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local keyword strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local keyword strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local keyword strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Local Keyword Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/local-link-building/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/local-link-building/SKILL.md new file mode 100644 index 0000000..d78cc40 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/local-link-building/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a local link building with structured process, quality checks, and system integration +--- + +# Local Link Building + +## Purpose + +Create a comprehensive local link building that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local link building documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local link building +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local link building using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Local Link Building + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/local-seo-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/local-seo-audit/SKILL.md new file mode 100644 index 0000000..17d79a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/local-seo-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a local seo audit with structured process, quality checks, and system integration +--- + +# Local Seo Audit + +## Purpose + +Analyze and produce a comprehensive local seo audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing local seo audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the local seo audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the local seo audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Local Seo Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/long-tail-keyword-finder/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/long-tail-keyword-finder/SKILL.md new file mode 100644 index 0000000..57eb006 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/long-tail-keyword-finder/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a long tail keyword finder with structured process, quality checks, and system integration +--- + +# Long Tail Keyword Finder + +## Purpose + +Create a comprehensive long tail keyword finder that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing long tail keyword finder documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the long tail keyword finder +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the long tail keyword finder using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Long Tail Keyword Finder + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/meta-description-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/meta-description-optimization/SKILL.md new file mode 100644 index 0000000..e1fc939 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/meta-description-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a meta description optimization with structured process, quality checks, and system integration +--- + +# Meta Description Optimization + +## Purpose + +Create a comprehensive meta description optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meta description optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meta description optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meta description optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Meta Description Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/meta-title-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/meta-title-optimization/SKILL.md new file mode 100644 index 0000000..7003c7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/meta-title-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a meta title optimization with structured process, quality checks, and system integration +--- + +# Meta Title Optimization + +## Purpose + +Create a comprehensive meta title optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing meta title optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the meta title optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the meta title optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Meta Title Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/multilingual-seo-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/multilingual-seo-strategy/SKILL.md new file mode 100644 index 0000000..c24e70c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/multilingual-seo-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a multilingual seo strategy with structured process, quality checks, and system integration +--- + +# Multilingual Seo Strategy + +## Purpose + +Design and document a comprehensive multilingual seo strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing multilingual seo strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the multilingual seo strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the multilingual seo strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Multilingual Seo Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/on-page-seo-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/on-page-seo-audit/SKILL.md new file mode 100644 index 0000000..b324d85 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/on-page-seo-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a on page seo audit with structured process, quality checks, and system integration +--- + +# On Page Seo Audit + +## Purpose + +Analyze and produce a comprehensive on page seo audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing on page seo audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the on page seo audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the on page seo audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# On Page Seo Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/podcast-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/podcast-seo/SKILL.md new file mode 100644 index 0000000..987ab49 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/podcast-seo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a podcast seo with structured process, quality checks, and system integration +--- + +# Podcast Seo + +## Purpose + +Create a comprehensive podcast seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing podcast seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the podcast seo +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the podcast seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Podcast Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/product-page-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/product-page-seo/SKILL.md new file mode 100644 index 0000000..644684f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/product-page-seo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product page seo with structured process, quality checks, and system integration +--- + +# Product Page Seo + +## Purpose + +Create a comprehensive product page seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product page seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product page seo +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product page seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Product Page Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/question-keyword-research/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/question-keyword-research/SKILL.md new file mode 100644 index 0000000..06c10c4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/question-keyword-research/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a question keyword research with structured process, quality checks, and system integration +--- + +# Question Keyword Research + +## Purpose + +Create a comprehensive question keyword research that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing question keyword research documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the question keyword research +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the question keyword research using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Question Keyword Research + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/redirect-map/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/redirect-map/SKILL.md new file mode 100644 index 0000000..60a4f14 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/redirect-map/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a redirect map with structured process, quality checks, and system integration +--- + +# Redirect Map + +## Purpose + +Create a comprehensive redirect map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing redirect map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the redirect map +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the redirect map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Redirect Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/review-generation-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/review-generation-plan/SKILL.md new file mode 100644 index 0000000..f2a5405 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/review-generation-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a review generation plan with structured process, quality checks, and system integration +--- + +# Review Generation Plan + +## Purpose + +Analyze and produce a comprehensive review generation plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review generation plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review generation plan +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review generation plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Review Generation Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/robots-txt-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/robots-txt-optimization/SKILL.md new file mode 100644 index 0000000..c9868fd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/robots-txt-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a robots txt optimization with structured process, quality checks, and system integration +--- + +# Robots Txt Optimization + +## Purpose + +Create a comprehensive robots txt optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing robots txt optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the robots txt optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the robots txt optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Robots Txt Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/schema-markup-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/schema-markup-generator/SKILL.md new file mode 100644 index 0000000..c7c64f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/schema-markup-generator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a schema markup generator with structured process, quality checks, and system integration +--- + +# Schema Markup Generator + +## Purpose + +Create a comprehensive schema markup generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing schema markup generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the schema markup generator +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the schema markup generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Schema Markup Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/search-intent-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/search-intent-analysis/SKILL.md new file mode 100644 index 0000000..fab9c48 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/search-intent-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a search intent analysis with structured process, quality checks, and system integration +--- + +# Search Intent Analysis + +## Purpose + +Analyze and produce a comprehensive search intent analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing search intent analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the search intent analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the search intent analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Search Intent Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/seo-content-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/seo-content-audit/SKILL.md new file mode 100644 index 0000000..b6aeb4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/seo-content-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a seo content audit with structured process, quality checks, and system integration +--- + +# Seo Content Audit + +## Purpose + +Analyze and produce a comprehensive seo content audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seo content audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seo content audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seo content audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Seo Content Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/seo-content-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/seo-content-outline/SKILL.md new file mode 100644 index 0000000..591c705 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/seo-content-outline/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a seo content outline with structured process, quality checks, and system integration +--- + +# Seo Content Outline + +## Purpose + +Create a comprehensive seo content outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seo content outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seo content outline +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seo content outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Seo Content Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/seo-forecast/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/seo-forecast/SKILL.md new file mode 100644 index 0000000..6d3ff14 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/seo-forecast/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a seo forecast with structured process, quality checks, and system integration +--- + +# Seo Forecast + +## Purpose + +Analyze and produce a comprehensive seo forecast that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seo forecast documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seo forecast +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seo forecast using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Seo Forecast + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/seo-reporting-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/seo-reporting-dashboard/SKILL.md new file mode 100644 index 0000000..fec395e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/seo-reporting-dashboard/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a seo reporting dashboard with structured process, quality checks, and system integration +--- + +# Seo Reporting Dashboard + +## Purpose + +Analyze and produce a comprehensive seo reporting dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seo reporting dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seo reporting dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seo reporting dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Seo Reporting Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/seo-roadmap/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/seo-roadmap/SKILL.md new file mode 100644 index 0000000..d69d09f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/seo-roadmap/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a seo roadmap with structured process, quality checks, and system integration +--- + +# Seo Roadmap + +## Purpose + +Design and document a comprehensive seo roadmap that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seo roadmap documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seo roadmap +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seo roadmap using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Seo Roadmap + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/serp-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/serp-analysis/SKILL.md new file mode 100644 index 0000000..8021b01 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/serp-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a serp analysis with structured process, quality checks, and system integration +--- + +# Serp Analysis + +## Purpose + +Analyze and produce a comprehensive serp analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing serp analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the serp analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the serp analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Serp Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/site-speed-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/site-speed-analysis/SKILL.md new file mode 100644 index 0000000..b35f566 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/site-speed-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a site speed analysis with structured process, quality checks, and system integration +--- + +# Site Speed Analysis + +## Purpose + +Analyze and produce a comprehensive site speed analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing site speed analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the site speed analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the site speed analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Site Speed Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/technical-seo-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/technical-seo-audit/SKILL.md new file mode 100644 index 0000000..af5cc08 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/technical-seo-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a technical seo audit with structured process, quality checks, and system integration +--- + +# Technical Seo Audit + +## Purpose + +Analyze and produce a comprehensive technical seo audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing technical seo audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the technical seo audit +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the technical seo audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Technical Seo Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/topical-authority-map/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/topical-authority-map/SKILL.md new file mode 100644 index 0000000..827a647 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/topical-authority-map/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a topical authority map with structured process, quality checks, and system integration +--- + +# Topical Authority Map + +## Purpose + +Create a comprehensive topical authority map that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing topical authority map documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the topical authority map +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the topical authority map using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Topical Authority Map + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/xml-sitemap-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/xml-sitemap-optimization/SKILL.md new file mode 100644 index 0000000..bdd82ea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/xml-sitemap-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a xml sitemap optimization with structured process, quality checks, and system integration +--- + +# Xml Sitemap Optimization + +## Purpose + +Create a comprehensive xml sitemap optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing xml sitemap optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the xml sitemap optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the xml sitemap optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Xml Sitemap Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/seo/youtube-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/seo/youtube-seo/SKILL.md new file mode 100644 index 0000000..d691a9a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/seo/youtube-seo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a youtube seo with structured process, quality checks, and system integration +--- + +# Youtube Seo + +## Purpose + +Create a comprehensive youtube seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: SEO & Search + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Topical Authority, E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Search Intent Classification (Informational/Navigational/Transactional/Commercial) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube seo +- Identify gaps, opportunities, and risks +- Define success metrics: Organic Traffic, Keyword Rankings, Click-Through Rate, Domain Authority +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Target one primary keyword per page + +## Output Format + +```markdown +# Youtube Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Topical Authority +- E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) +- Search Intent Classification (Informational/Navigational/Transactional/Commercial) +- Pillar-Cluster Model +- Technical SEO Pyramid + +## Key Metrics +- Organic Traffic +- Keyword Rankings +- Click-Through Rate +- Domain Authority +- Page Speed (Core Web Vitals) +- Crawl Budget +- Index Coverage + +## Best Practices +- Target one primary keyword per page +- Title tags under 60 chars, meta descriptions 150-160 chars +- Internal link every 200-300 words +- Update content every 6-12 months +- Page load under 2.5 seconds (LCP) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/bluesky-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/bluesky-post/SKILL.md new file mode 100644 index 0000000..a786ca5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/bluesky-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a bluesky post with structured process, quality checks, and system integration +--- + +# Bluesky Post + +## Purpose + +Create a comprehensive bluesky post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bluesky post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bluesky post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bluesky post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Bluesky Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/brand-ambassador-program/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/brand-ambassador-program/SKILL.md new file mode 100644 index 0000000..30ab896 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/brand-ambassador-program/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a brand ambassador program with structured process, quality checks, and system integration +--- + +# Brand Ambassador Program + +## Purpose + +Design and document a comprehensive brand ambassador program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand ambassador program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand ambassador program +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand ambassador program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Brand Ambassador Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/community-guidelines/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/community-guidelines/SKILL.md new file mode 100644 index 0000000..75858de --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/community-guidelines/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a community guidelines with structured process, quality checks, and system integration +--- + +# Community Guidelines + +## Purpose + +Design and document a comprehensive community guidelines that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing community guidelines documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the community guidelines +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the community guidelines using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Community Guidelines + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/creator-partnership/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/creator-partnership/SKILL.md new file mode 100644 index 0000000..ccb58c3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/creator-partnership/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a creator partnership with structured process, quality checks, and system integration +--- + +# Creator Partnership + +## Purpose + +Create a comprehensive creator partnership that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing creator partnership documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the creator partnership +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the creator partnership using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Creator Partnership + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/cross-platform-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/cross-platform-strategy/SKILL.md new file mode 100644 index 0000000..ae18e3b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/cross-platform-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a cross platform strategy with structured process, quality checks, and system integration +--- + +# Cross Platform Strategy + +## Purpose + +Design and document a comprehensive cross platform strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cross platform strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cross platform strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cross platform strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Cross Platform Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/employee-advocacy-program/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/employee-advocacy-program/SKILL.md new file mode 100644 index 0000000..a83e48a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/employee-advocacy-program/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a employee advocacy program with structured process, quality checks, and system integration +--- + +# Employee Advocacy Program + +## Purpose + +Design and document a comprehensive employee advocacy program that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing employee advocacy program documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the employee advocacy program +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the employee advocacy program using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Employee Advocacy Program + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/engagement-rate-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/engagement-rate-analysis/SKILL.md new file mode 100644 index 0000000..7080c46 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/engagement-rate-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a engagement rate analysis with structured process, quality checks, and system integration +--- + +# Engagement Rate Analysis + +## Purpose + +Analyze and produce a comprehensive engagement rate analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing engagement rate analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the engagement rate analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the engagement rate analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Engagement Rate Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/executive-social-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/executive-social-strategy/SKILL.md new file mode 100644 index 0000000..f1439cf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/executive-social-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a executive social strategy with structured process, quality checks, and system integration +--- + +# Executive Social Strategy + +## Purpose + +Design and document a comprehensive executive social strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing executive social strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the executive social strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the executive social strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Executive Social Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/facebook-event-promotion/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/facebook-event-promotion/SKILL.md new file mode 100644 index 0000000..07b13ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/facebook-event-promotion/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a facebook event promotion with structured process, quality checks, and system integration +--- + +# Facebook Event Promotion + +## Purpose + +Create a comprehensive facebook event promotion that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing facebook event promotion documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the facebook event promotion +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the facebook event promotion using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Facebook Event Promotion + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/facebook-group-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/facebook-group-strategy/SKILL.md new file mode 100644 index 0000000..40b93d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/facebook-group-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a facebook group strategy with structured process, quality checks, and system integration +--- + +# Facebook Group Strategy + +## Purpose + +Design and document a comprehensive facebook group strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing facebook group strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the facebook group strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the facebook group strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Facebook Group Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/facebook-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/facebook-post/SKILL.md new file mode 100644 index 0000000..e0b9d60 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/facebook-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a facebook post with structured process, quality checks, and system integration +--- + +# Facebook Post + +## Purpose + +Create a comprehensive facebook post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing facebook post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the facebook post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the facebook post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Facebook Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/follower-growth-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/follower-growth-strategy/SKILL.md new file mode 100644 index 0000000..c273d00 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/follower-growth-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a follower growth strategy with structured process, quality checks, and system integration +--- + +# Follower Growth Strategy + +## Purpose + +Design and document a comprehensive follower growth strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing follower growth strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the follower growth strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the follower growth strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Follower Growth Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/influencer-collaboration-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/influencer-collaboration-brief/SKILL.md new file mode 100644 index 0000000..cde7349 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/influencer-collaboration-brief/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a influencer collaboration brief with structured process, quality checks, and system integration +--- + +# Influencer Collaboration Brief + +## Purpose + +Create a comprehensive influencer collaboration brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing influencer collaboration brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the influencer collaboration brief +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the influencer collaboration brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Influencer Collaboration Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-bio-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-bio-optimization/SKILL.md new file mode 100644 index 0000000..243f3b8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-bio-optimization/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a instagram bio optimization with structured process, quality checks, and system integration +--- + +# Instagram Bio Optimization + +## Purpose + +Create a comprehensive instagram bio optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram bio optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram bio optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram bio optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Bio Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-carousel/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-carousel/SKILL.md new file mode 100644 index 0000000..25419c0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-carousel/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a instagram carousel with structured process, quality checks, and system integration +--- + +# Instagram Carousel + +## Purpose + +Create a comprehensive instagram carousel that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram carousel documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram carousel +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram carousel using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Carousel + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-hashtag-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-hashtag-strategy/SKILL.md new file mode 100644 index 0000000..cdb97fa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-hashtag-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a instagram hashtag strategy with structured process, quality checks, and system integration +--- + +# Instagram Hashtag Strategy + +## Purpose + +Design and document a comprehensive instagram hashtag strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram hashtag strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram hashtag strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram hashtag strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Hashtag Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-post/SKILL.md new file mode 100644 index 0000000..24db42d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a instagram post with structured process, quality checks, and system integration +--- + +# Instagram Post + +## Purpose + +Create a comprehensive instagram post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-reel-script/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-reel-script/SKILL.md new file mode 100644 index 0000000..9fb218e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-reel-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a instagram reel script with structured process, quality checks, and system integration +--- + +# Instagram Reel Script + +## Purpose + +Create a comprehensive instagram reel script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram reel script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram reel script +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram reel script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Reel Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/instagram-story-sequence/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/instagram-story-sequence/SKILL.md new file mode 100644 index 0000000..268c5ba --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/instagram-story-sequence/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a instagram story sequence with structured process, quality checks, and system integration +--- + +# Instagram Story Sequence + +## Purpose + +Create a comprehensive instagram story sequence that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing instagram story sequence documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the instagram story sequence +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the instagram story sequence using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Instagram Story Sequence + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-article/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-article/SKILL.md new file mode 100644 index 0000000..57345e8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-article/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin article with structured process, quality checks, and system integration +--- + +# Linkedin Article + +## Purpose + +Create a comprehensive linkedin article that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin article documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin article +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin article using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Article + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-carousel/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-carousel/SKILL.md new file mode 100644 index 0000000..234e25a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-carousel/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin carousel with structured process, quality checks, and system integration +--- + +# Linkedin Carousel + +## Purpose + +Create a comprehensive linkedin carousel that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin carousel documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin carousel +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin carousel using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Carousel + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-company-page/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-company-page/SKILL.md new file mode 100644 index 0000000..46d89f2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-company-page/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin company page with structured process, quality checks, and system integration +--- + +# Linkedin Company Page + +## Purpose + +Create a comprehensive linkedin company page that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin company page documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin company page +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin company page using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Company Page + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-outreach/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-outreach/SKILL.md new file mode 100644 index 0000000..4effd5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-outreach/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin outreach with structured process, quality checks, and system integration +--- + +# Linkedin Outreach + +## Purpose + +Create a comprehensive linkedin outreach that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin outreach documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin outreach +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin outreach using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Outreach + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-post/SKILL.md new file mode 100644 index 0000000..42b5847 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin post with structured process, quality checks, and system integration +--- + +# Linkedin Post + +## Purpose + +Create a comprehensive linkedin post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/linkedin-profile-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/linkedin-profile-optimization/SKILL.md new file mode 100644 index 0000000..ae84c77 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/linkedin-profile-optimization/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a linkedin profile optimization with structured process, quality checks, and system integration +--- + +# Linkedin Profile Optimization + +## Purpose + +Create a comprehensive linkedin profile optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing linkedin profile optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the linkedin profile optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the linkedin profile optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Linkedin Profile Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/mastodon-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/mastodon-post/SKILL.md new file mode 100644 index 0000000..d1c9255 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/mastodon-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a mastodon post with structured process, quality checks, and system integration +--- + +# Mastodon Post + +## Purpose + +Create a comprehensive mastodon post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mastodon post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mastodon post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mastodon post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Mastodon Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/negative-comment-response/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/negative-comment-response/SKILL.md new file mode 100644 index 0000000..b0ba92b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/negative-comment-response/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a negative comment response with structured process, quality checks, and system integration +--- + +# Negative Comment Response + +## Purpose + +Create a comprehensive negative comment response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing negative comment response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the negative comment response +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the negative comment response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Negative Comment Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/pinterest-board-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/pinterest-board-strategy/SKILL.md new file mode 100644 index 0000000..2b9536b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/pinterest-board-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a pinterest board strategy with structured process, quality checks, and system integration +--- + +# Pinterest Board Strategy + +## Purpose + +Design and document a comprehensive pinterest board strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pinterest board strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pinterest board strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pinterest board strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Pinterest Board Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/pinterest-pin/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/pinterest-pin/SKILL.md new file mode 100644 index 0000000..09774e6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/pinterest-pin/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a pinterest pin with structured process, quality checks, and system integration +--- + +# Pinterest Pin + +## Purpose + +Create a comprehensive pinterest pin that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pinterest pin documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pinterest pin +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pinterest pin using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Pinterest Pin + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/pinterest-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/pinterest-seo/SKILL.md new file mode 100644 index 0000000..4c70f8e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/pinterest-seo/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a pinterest seo with structured process, quality checks, and system integration +--- + +# Pinterest Seo + +## Purpose + +Create a comprehensive pinterest seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pinterest seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pinterest seo +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pinterest seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Pinterest Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/platform-migration-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/platform-migration-plan/SKILL.md new file mode 100644 index 0000000..f75acea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/platform-migration-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a platform migration plan with structured process, quality checks, and system integration +--- + +# Platform Migration Plan + +## Purpose + +Design and document a comprehensive platform migration plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing platform migration plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the platform migration plan +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the platform migration plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Platform Migration Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/reddit-ama-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/reddit-ama-plan/SKILL.md new file mode 100644 index 0000000..41dab4d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/reddit-ama-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a reddit ama plan with structured process, quality checks, and system integration +--- + +# Reddit Ama Plan + +## Purpose + +Design and document a comprehensive reddit ama plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reddit ama plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reddit ama plan +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reddit ama plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Reddit Ama Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/reddit-community-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/reddit-community-strategy/SKILL.md new file mode 100644 index 0000000..e07199a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/reddit-community-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a reddit community strategy with structured process, quality checks, and system integration +--- + +# Reddit Community Strategy + +## Purpose + +Design and document a comprehensive reddit community strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reddit community strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reddit community strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reddit community strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Reddit Community Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/reddit-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/reddit-post/SKILL.md new file mode 100644 index 0000000..a1d320f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/reddit-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a reddit post with structured process, quality checks, and system integration +--- + +# Reddit Post + +## Purpose + +Create a comprehensive reddit post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing reddit post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the reddit post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the reddit post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Reddit Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/review-response/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/review-response/SKILL.md new file mode 100644 index 0000000..21e8f20 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/review-response/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a review response with structured process, quality checks, and system integration +--- + +# Review Response + +## Purpose + +Analyze and produce a comprehensive review response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing review response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the review response +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the review response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Review Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/sentiment-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/sentiment-analysis/SKILL.md new file mode 100644 index 0000000..3deda8e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/sentiment-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a sentiment analysis with structured process, quality checks, and system integration +--- + +# Sentiment Analysis + +## Purpose + +Analyze and produce a comprehensive sentiment analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sentiment analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sentiment analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sentiment analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Sentiment Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-audit/SKILL.md new file mode 100644 index 0000000..29326ef --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-audit/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a social audit with structured process, quality checks, and system integration +--- + +# Social Audit + +## Purpose + +Analyze and produce a comprehensive social audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social audit +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-content-calendar/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-content-calendar/SKILL.md new file mode 100644 index 0000000..bbc647b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-content-calendar/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a social content calendar with structured process, quality checks, and system integration +--- + +# Social Content Calendar + +## Purpose + +Design and document a comprehensive social content calendar that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social content calendar documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social content calendar +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social content calendar using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Content Calendar + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-contest/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-contest/SKILL.md new file mode 100644 index 0000000..276f6fe --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-contest/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social contest with structured process, quality checks, and system integration +--- + +# Social Contest + +## Purpose + +Create a comprehensive social contest that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social contest documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social contest +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social contest using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Contest + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-listening-report/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-listening-report/SKILL.md new file mode 100644 index 0000000..2642239 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-listening-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a social listening report with structured process, quality checks, and system integration +--- + +# Social Listening Report + +## Purpose + +Analyze and produce a comprehensive social listening report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social listening report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social listening report +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social listening report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Listening Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-media-bio-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-media-bio-generator/SKILL.md new file mode 100644 index 0000000..9d15f18 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-media-bio-generator/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social media bio generator with structured process, quality checks, and system integration +--- + +# Social Media Bio Generator + +## Purpose + +Create a comprehensive social media bio generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media bio generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media bio generator +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media bio generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Media Bio Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-media-crisis-response/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-media-crisis-response/SKILL.md new file mode 100644 index 0000000..abfca5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-media-crisis-response/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social media crisis response with structured process, quality checks, and system integration +--- + +# Social Media Crisis Response + +## Purpose + +Create a comprehensive social media crisis response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media crisis response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media crisis response +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media crisis response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Media Crisis Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-media-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-media-policy/SKILL.md new file mode 100644 index 0000000..ef7a61d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-media-policy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social media policy with structured process, quality checks, and system integration +--- + +# Social Media Policy + +## Purpose + +Create a comprehensive social media policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media policy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Media Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-media-response/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-media-response/SKILL.md new file mode 100644 index 0000000..964b485 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-media-response/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social media response with structured process, quality checks, and system integration +--- + +# Social Media Response + +## Purpose + +Create a comprehensive social media response that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social media response documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social media response +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social media response using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Media Response + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-selling/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-selling/SKILL.md new file mode 100644 index 0000000..6aa9cf9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-selling/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a social selling with structured process, quality checks, and system integration +--- + +# Social Selling + +## Purpose + +Create a comprehensive social selling that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social selling documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social selling +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social selling using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Selling + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/social-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/social-strategy/SKILL.md new file mode 100644 index 0000000..5153d98 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/social-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a social strategy with structured process, quality checks, and system integration +--- + +# Social Strategy + +## Purpose + +Design and document a comprehensive social strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing social strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the social strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the social strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Social Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/threads-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/threads-post/SKILL.md new file mode 100644 index 0000000..ed92dfd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/threads-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a threads post with structured process, quality checks, and system integration +--- + +# Threads Post + +## Purpose + +Create a comprehensive threads post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing threads post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the threads post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the threads post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Threads Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-content-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-content-strategy/SKILL.md new file mode 100644 index 0000000..abb87ca --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-content-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a tiktok content strategy with structured process, quality checks, and system integration +--- + +# Tiktok Content Strategy + +## Purpose + +Design and document a comprehensive tiktok content strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok content strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok content strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok content strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Content Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-duet-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-duet-strategy/SKILL.md new file mode 100644 index 0000000..9ab153d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-duet-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a tiktok duet strategy with structured process, quality checks, and system integration +--- + +# Tiktok Duet Strategy + +## Purpose + +Design and document a comprehensive tiktok duet strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok duet strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok duet strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok duet strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Duet Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-hook-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-hook-generator/SKILL.md new file mode 100644 index 0000000..66e7388 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-hook-generator/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a tiktok hook generator with structured process, quality checks, and system integration +--- + +# Tiktok Hook Generator + +## Purpose + +Create a comprehensive tiktok hook generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok hook generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok hook generator +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok hook generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Hook Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-script/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-script/SKILL.md new file mode 100644 index 0000000..43fb102 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a tiktok script with structured process, quality checks, and system integration +--- + +# Tiktok Script + +## Purpose + +Create a comprehensive tiktok script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok script +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-series-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-series-plan/SKILL.md new file mode 100644 index 0000000..168de4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-series-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a tiktok series plan with structured process, quality checks, and system integration +--- + +# Tiktok Series Plan + +## Purpose + +Design and document a comprehensive tiktok series plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok series plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok series plan +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok series plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Series Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/tiktok-trend-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/tiktok-trend-analysis/SKILL.md new file mode 100644 index 0000000..c135649 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/tiktok-trend-analysis/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a tiktok trend analysis with structured process, quality checks, and system integration +--- + +# Tiktok Trend Analysis + +## Purpose + +Analyze and produce a comprehensive tiktok trend analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tiktok trend analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tiktok trend analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tiktok trend analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Tiktok Trend Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/trend-report/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/trend-report/SKILL.md new file mode 100644 index 0000000..3f1d3f3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/trend-report/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Analyze and produce a trend report with structured process, quality checks, and system integration +--- + +# Trend Report + +## Purpose + +Analyze and produce a comprehensive trend report that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trend report documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trend report +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trend report using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Trend Report + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-engagement-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-engagement-strategy/SKILL.md new file mode 100644 index 0000000..ed3f00e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-engagement-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a twitter engagement strategy with structured process, quality checks, and system integration +--- + +# Twitter Engagement Strategy + +## Purpose + +Design and document a comprehensive twitter engagement strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter engagement strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter engagement strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter engagement strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Engagement Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-growth-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-growth-strategy/SKILL.md new file mode 100644 index 0000000..2449d27 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-growth-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a twitter growth strategy with structured process, quality checks, and system integration +--- + +# Twitter Growth Strategy + +## Purpose + +Design and document a comprehensive twitter growth strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter growth strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter growth strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter growth strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Growth Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-post/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-post/SKILL.md new file mode 100644 index 0000000..079cc12 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-post/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a twitter post with structured process, quality checks, and system integration +--- + +# Twitter Post + +## Purpose + +Create a comprehensive twitter post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter post +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-profile-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-profile-optimization/SKILL.md new file mode 100644 index 0000000..fa8c054 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-profile-optimization/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a twitter profile optimization with structured process, quality checks, and system integration +--- + +# Twitter Profile Optimization + +## Purpose + +Create a comprehensive twitter profile optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter profile optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter profile optimization +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter profile optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Profile Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-spaces-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-spaces-plan/SKILL.md new file mode 100644 index 0000000..cd5b040 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-spaces-plan/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a twitter spaces plan with structured process, quality checks, and system integration +--- + +# Twitter Spaces Plan + +## Purpose + +Design and document a comprehensive twitter spaces plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter spaces plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter spaces plan +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter spaces plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Spaces Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/twitter-thread/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/twitter-thread/SKILL.md new file mode 100644 index 0000000..f00ed44 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/twitter-thread/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a twitter thread with structured process, quality checks, and system integration +--- + +# Twitter Thread + +## Purpose + +Create a comprehensive twitter thread that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing twitter thread documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the twitter thread +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the twitter thread using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Twitter Thread + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/ugc-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/ugc-strategy/SKILL.md new file mode 100644 index 0000000..898b2a4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/ugc-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a ugc strategy with structured process, quality checks, and system integration +--- + +# Ugc Strategy + +## Purpose + +Design and document a comprehensive ugc strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ugc strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ugc strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ugc strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Ugc Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/user-generated-content-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/user-generated-content-brief/SKILL.md new file mode 100644 index 0000000..b0bfdb7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/user-generated-content-brief/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a user generated content brief with structured process, quality checks, and system integration +--- + +# User Generated Content Brief + +## Purpose + +Create a comprehensive user generated content brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing user generated content brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the user generated content brief +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the user generated content brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# User Generated Content Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/viral-content-formula/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/viral-content-formula/SKILL.md new file mode 100644 index 0000000..6df6917 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/viral-content-formula/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a viral content formula with structured process, quality checks, and system integration +--- + +# Viral Content Formula + +## Purpose + +Create a comprehensive viral content formula that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing viral content formula documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the viral content formula +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the viral content formula using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Viral Content Formula + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-channel-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-channel-strategy/SKILL.md new file mode 100644 index 0000000..cad10d1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-channel-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a youtube channel strategy with structured process, quality checks, and system integration +--- + +# Youtube Channel Strategy + +## Purpose + +Design and document a comprehensive youtube channel strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube channel strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube channel strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube channel strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Channel Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-description-seo/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-description-seo/SKILL.md new file mode 100644 index 0000000..bea0e5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-description-seo/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a youtube description seo with structured process, quality checks, and system integration +--- + +# Youtube Description Seo + +## Purpose + +Create a comprehensive youtube description seo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube description seo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube description seo +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube description seo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Description Seo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-playlist-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-playlist-strategy/SKILL.md new file mode 100644 index 0000000..99d188f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-playlist-strategy/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Design and document a youtube playlist strategy with structured process, quality checks, and system integration +--- + +# Youtube Playlist Strategy + +## Purpose + +Design and document a comprehensive youtube playlist strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube playlist strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube playlist strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube playlist strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Playlist Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-shorts-script/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-shorts-script/SKILL.md new file mode 100644 index 0000000..6aff705 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-shorts-script/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a youtube shorts script with structured process, quality checks, and system integration +--- + +# Youtube Shorts Script + +## Purpose + +Create a comprehensive youtube shorts script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube shorts script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube shorts script +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube shorts script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Shorts Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-title-thumbnail/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-title-thumbnail/SKILL.md new file mode 100644 index 0000000..034813d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-title-thumbnail/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a youtube title thumbnail with structured process, quality checks, and system integration +--- + +# Youtube Title Thumbnail + +## Purpose + +Create a comprehensive youtube title thumbnail that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube title thumbnail documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube title thumbnail +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube title thumbnail using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Title Thumbnail + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/social-media/youtube-video-outline/SKILL.md b/clowdex-download/.claude/.claude/skills/social-media/youtube-video-outline/SKILL.md new file mode 100644 index 0000000..a13feb1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/social-media/youtube-video-outline/SKILL.md @@ -0,0 +1,133 @@ +--- +description: Create a youtube video outline with structured process, quality checks, and system integration +--- + +# Youtube Video Outline + +## Purpose + +Create a comprehensive youtube video outline that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Social Media + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Target Audience**: Who this is for (demographics, psychographics, pain points) + +### Optional +- **Brand Voice**: Tone and style guidelines (check knowledge-base for existing) +- **Competitors**: Key competitors to differentiate from + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing youtube video outline documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Content Pillars (3-5 themes), Hero/Hub/Hygiene, 80/20 Rule (value/promotion) + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the youtube video outline +- Identify gaps, opportunities, and risks +- Define success metrics: Engagement Rate, Reach, Impressions, Follower Growth Rate +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the youtube video outline using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Post when your audience is online (check analytics) + +## Output Format + +```markdown +# Youtube Video Outline + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Content Pillars (3-5 themes) +- Hero/Hub/Hygiene +- 80/20 Rule (value/promotion) +- Platform-native content +- Community-Led Growth + +## Key Metrics +- Engagement Rate +- Reach +- Impressions +- Follower Growth Rate +- Click-Through Rate +- Share Rate +- Save Rate +- Story Completion Rate + +## Best Practices +- Post when your audience is online (check analytics) +- Respond to comments within 1 hour +- Repurpose one piece of content across 5+ formats +- Use platform-native features (polls, stickers, carousels) +- Hook in first 3 seconds (video) or first line (text) + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/accelerator-application/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/accelerator-application/SKILL.md new file mode 100644 index 0000000..ec81e58 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/accelerator-application/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a accelerator application with structured process, quality checks, and system integration +--- + +# Accelerator Application + +## Purpose + +Create a comprehensive accelerator application that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing accelerator application documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the accelerator application +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the accelerator application using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Accelerator Application + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/acquisition-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/acquisition-prep/SKILL.md new file mode 100644 index 0000000..ad33193 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/acquisition-prep/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a acquisition prep with structured process, quality checks, and system integration +--- + +# Acquisition Prep + +## Purpose + +Create a comprehensive acquisition prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing acquisition prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the acquisition prep +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the acquisition prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Acquisition Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/advisory-board-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/advisory-board-setup/SKILL.md new file mode 100644 index 0000000..be32bf5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/advisory-board-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a advisory board setup with structured process, quality checks, and system integration +--- + +# Advisory Board Setup + +## Purpose + +Design and document a comprehensive advisory board setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing advisory board setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the advisory board setup +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the advisory board setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Advisory Board Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/board-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/board-deck/SKILL.md new file mode 100644 index 0000000..95b6da9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/board-deck/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a board deck with structured process, quality checks, and system integration +--- + +# Board Deck + +## Purpose + +Create a comprehensive board deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing board deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the board deck +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the board deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Board Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/bootstrap-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/bootstrap-plan/SKILL.md new file mode 100644 index 0000000..9d25ca5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/bootstrap-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a bootstrap plan with structured process, quality checks, and system integration +--- + +# Bootstrap Plan + +## Purpose + +Design and document a comprehensive bootstrap plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bootstrap plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bootstrap plan +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bootstrap plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Bootstrap Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/brand-name-generator/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/brand-name-generator/SKILL.md new file mode 100644 index 0000000..04d866a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/brand-name-generator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a brand name generator with structured process, quality checks, and system integration +--- + +# Brand Name Generator + +## Purpose + +Create a comprehensive brand name generator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing brand name generator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the brand name generator +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the brand name generator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Brand Name Generator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/build-measure-learn/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/build-measure-learn/SKILL.md new file mode 100644 index 0000000..9c69e7a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/build-measure-learn/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a build measure learn with structured process, quality checks, and system integration +--- + +# Build Measure Learn + +## Purpose + +Create a comprehensive build measure learn that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing build measure learn documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the build measure learn +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the build measure learn using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Build Measure Learn + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/business-model-canvas/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/business-model-canvas/SKILL.md new file mode 100644 index 0000000..9622209 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/business-model-canvas/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a business model canvas with structured process, quality checks, and system integration +--- + +# Business Model Canvas + +## Purpose + +Design and document a comprehensive business model canvas that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business model canvas documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business model canvas +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business model canvas using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Business Model Canvas + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/business-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/business-plan/SKILL.md new file mode 100644 index 0000000..3ec1ff4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/business-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a business plan with structured process, quality checks, and system integration +--- + +# Business Plan + +## Purpose + +Design and document a comprehensive business plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing business plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the business plan +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the business plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Business Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/cap-table-management/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/cap-table-management/SKILL.md new file mode 100644 index 0000000..afcb469 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/cap-table-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a cap table management with structured process, quality checks, and system integration +--- + +# Cap Table Management + +## Purpose + +Create a comprehensive cap table management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cap table management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cap table management +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cap table management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Cap Table Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/co-founder-agreement/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/co-founder-agreement/SKILL.md new file mode 100644 index 0000000..541905d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/co-founder-agreement/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a co founder agreement with structured process, quality checks, and system integration +--- + +# Co Founder Agreement + +## Purpose + +Create a comprehensive co founder agreement that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing co founder agreement documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the co founder agreement +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the co founder agreement using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Co Founder Agreement + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/competitive-landscape/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/competitive-landscape/SKILL.md new file mode 100644 index 0000000..64bd167 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/competitive-landscape/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a competitive landscape with structured process, quality checks, and system integration +--- + +# Competitive Landscape + +## Purpose + +Create a comprehensive competitive landscape that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing competitive landscape documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the competitive landscape +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the competitive landscape using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Competitive Landscape + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/culture-code/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/culture-code/SKILL.md new file mode 100644 index 0000000..aef6610 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/culture-code/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a culture code with structured process, quality checks, and system integration +--- + +# Culture Code + +## Purpose + +Create a comprehensive culture code that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing culture code documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the culture code +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the culture code using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Culture Code + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/customer-discovery/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/customer-discovery/SKILL.md new file mode 100644 index 0000000..6ec1742 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/customer-discovery/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a customer discovery with structured process, quality checks, and system integration +--- + +# Customer Discovery + +## Purpose + +Create a comprehensive customer discovery that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing customer discovery documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the customer discovery +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the customer discovery using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Customer Discovery + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/data-room-setup/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/data-room-setup/SKILL.md new file mode 100644 index 0000000..d8ee670 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/data-room-setup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a data room setup with structured process, quality checks, and system integration +--- + +# Data Room Setup + +## Purpose + +Design and document a comprehensive data room setup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing data room setup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the data room setup +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the data room setup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Data Room Setup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/defensibility-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/defensibility-assessment/SKILL.md new file mode 100644 index 0000000..47befae --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/defensibility-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a defensibility assessment with structured process, quality checks, and system integration +--- + +# Defensibility Assessment + +## Purpose + +Analyze and produce a comprehensive defensibility assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing defensibility assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the defensibility assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the defensibility assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Defensibility Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/distribution-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/distribution-strategy/SKILL.md new file mode 100644 index 0000000..4093d67 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/distribution-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a distribution strategy with structured process, quality checks, and system integration +--- + +# Distribution Strategy + +## Purpose + +Design and document a comprehensive distribution strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing distribution strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the distribution strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the distribution strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Distribution Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/domain-name-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/domain-name-strategy/SKILL.md new file mode 100644 index 0000000..fbc44d1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/domain-name-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a domain name strategy with structured process, quality checks, and system integration +--- + +# Domain Name Strategy + +## Purpose + +Design and document a comprehensive domain name strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing domain name strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the domain name strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the domain name strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Domain Name Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/due-diligence-prep/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/due-diligence-prep/SKILL.md new file mode 100644 index 0000000..e9ebf5a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/due-diligence-prep/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a due diligence prep with structured process, quality checks, and system integration +--- + +# Due Diligence Prep + +## Purpose + +Create a comprehensive due diligence prep that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing due diligence prep documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the due diligence prep +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the due diligence prep using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Due Diligence Prep + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/equity-split/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/equity-split/SKILL.md new file mode 100644 index 0000000..e63fbc1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/equity-split/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a equity split with structured process, quality checks, and system integration +--- + +# Equity Split + +## Purpose + +Create a comprehensive equity split that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing equity split documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the equity split +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the equity split using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Equity Split + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/exit-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/exit-strategy/SKILL.md new file mode 100644 index 0000000..58ab3be --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/exit-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a exit strategy with structured process, quality checks, and system integration +--- + +# Exit Strategy + +## Purpose + +Design and document a comprehensive exit strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing exit strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the exit strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the exit strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Exit Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/fundraising-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/fundraising-strategy/SKILL.md new file mode 100644 index 0000000..790dc9c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/fundraising-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a fundraising strategy with structured process, quality checks, and system integration +--- + +# Fundraising Strategy + +## Purpose + +Design and document a comprehensive fundraising strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing fundraising strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the fundraising strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the fundraising strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Fundraising Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/growth-experiment-design/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/growth-experiment-design/SKILL.md new file mode 100644 index 0000000..fc63a20 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/growth-experiment-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a growth experiment design with structured process, quality checks, and system integration +--- + +# Growth Experiment Design + +## Purpose + +Create a comprehensive growth experiment design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing growth experiment design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the growth experiment design +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the growth experiment design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Growth Experiment Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/growth-metrics/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/growth-metrics/SKILL.md new file mode 100644 index 0000000..c31f418 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/growth-metrics/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a growth metrics with structured process, quality checks, and system integration +--- + +# Growth Metrics + +## Purpose + +Analyze and produce a comprehensive growth metrics that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing growth metrics documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the growth metrics +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the growth metrics using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Growth Metrics + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/growth-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/growth-strategy/SKILL.md new file mode 100644 index 0000000..ab779f4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/growth-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a growth strategy with structured process, quality checks, and system integration +--- + +# Growth Strategy + +## Purpose + +Design and document a comprehensive growth strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing growth strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the growth strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the growth strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Growth Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/hiring-first-ten/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/hiring-first-ten/SKILL.md new file mode 100644 index 0000000..790de4d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/hiring-first-ten/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a hiring first ten with structured process, quality checks, and system integration +--- + +# Hiring First Ten + +## Purpose + +Create a comprehensive hiring first ten that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hiring first ten documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hiring first ten +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hiring first ten using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Hiring First Ten + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/incorporation-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/incorporation-guide/SKILL.md new file mode 100644 index 0000000..654cda5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/incorporation-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a incorporation guide with structured process, quality checks, and system integration +--- + +# Incorporation Guide + +## Purpose + +Design and document a comprehensive incorporation guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing incorporation guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the incorporation guide +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the incorporation guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Incorporation Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/investor-outreach/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/investor-outreach/SKILL.md new file mode 100644 index 0000000..c5ca78c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/investor-outreach/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a investor outreach with structured process, quality checks, and system integration +--- + +# Investor Outreach + +## Purpose + +Create a comprehensive investor outreach that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor outreach documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor outreach +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor outreach using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Investor Outreach + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/investor-pitch-script/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/investor-pitch-script/SKILL.md new file mode 100644 index 0000000..5628caa --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/investor-pitch-script/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a investor pitch script with structured process, quality checks, and system integration +--- + +# Investor Pitch Script + +## Purpose + +Create a comprehensive investor pitch script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor pitch script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor pitch script +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor pitch script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Investor Pitch Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/investor-target-list/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/investor-target-list/SKILL.md new file mode 100644 index 0000000..1c2bd30 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/investor-target-list/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a investor target list with structured process, quality checks, and system integration +--- + +# Investor Target List + +## Purpose + +Create a comprehensive investor target list that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor target list documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor target list +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor target list using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Investor Target List + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/investor-update-template/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/investor-update-template/SKILL.md new file mode 100644 index 0000000..da18437 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/investor-update-template/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a investor update template with structured process, quality checks, and system integration +--- + +# Investor Update Template + +## Purpose + +Create a comprehensive investor update template that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing investor update template documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the investor update template +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the investor update template using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Investor Update Template + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/ipo-readiness/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/ipo-readiness/SKILL.md new file mode 100644 index 0000000..b55bda5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/ipo-readiness/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a ipo readiness with structured process, quality checks, and system integration +--- + +# Ipo Readiness + +## Purpose + +Create a comprehensive ipo readiness that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing ipo readiness documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the ipo readiness +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the ipo readiness using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Ipo Readiness + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/kill-criteria/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/kill-criteria/SKILL.md new file mode 100644 index 0000000..7fc52ad --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/kill-criteria/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a kill criteria with structured process, quality checks, and system integration +--- + +# Kill Criteria + +## Purpose + +Create a comprehensive kill criteria that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing kill criteria documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the kill criteria +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the kill criteria using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Kill Criteria + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/lean-canvas/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/lean-canvas/SKILL.md new file mode 100644 index 0000000..e3fb477 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/lean-canvas/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a lean canvas with structured process, quality checks, and system integration +--- + +# Lean Canvas + +## Purpose + +Create a comprehensive lean canvas that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing lean canvas documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the lean canvas +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the lean canvas using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Lean Canvas + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/market-validation/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/market-validation/SKILL.md new file mode 100644 index 0000000..abfff6b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/market-validation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a market validation with structured process, quality checks, and system integration +--- + +# Market Validation + +## Purpose + +Create a comprehensive market validation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing market validation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the market validation +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the market validation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Market Validation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/marketplace-launch/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/marketplace-launch/SKILL.md new file mode 100644 index 0000000..f1cf4c2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/marketplace-launch/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a marketplace launch with structured process, quality checks, and system integration +--- + +# Marketplace Launch + +## Purpose + +Create a comprehensive marketplace launch that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing marketplace launch documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the marketplace launch +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the marketplace launch using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Marketplace Launch + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/mentor-outreach/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/mentor-outreach/SKILL.md new file mode 100644 index 0000000..72f2646 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/mentor-outreach/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mentor outreach with structured process, quality checks, and system integration +--- + +# Mentor Outreach + +## Purpose + +Create a comprehensive mentor outreach that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mentor outreach documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mentor outreach +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mentor outreach using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Mentor Outreach + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/moat-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/moat-analysis/SKILL.md new file mode 100644 index 0000000..9c8f66c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/moat-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a moat analysis with structured process, quality checks, and system integration +--- + +# Moat Analysis + +## Purpose + +Analyze and produce a comprehensive moat analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing moat analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the moat analysis +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the moat analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Moat Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/monetization-strategy/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/monetization-strategy/SKILL.md new file mode 100644 index 0000000..eb52349 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/monetization-strategy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a monetization strategy with structured process, quality checks, and system integration +--- + +# Monetization Strategy + +## Purpose + +Design and document a comprehensive monetization strategy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing monetization strategy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the monetization strategy +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the monetization strategy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Monetization Strategy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/mvp-definition/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/mvp-definition/SKILL.md new file mode 100644 index 0000000..d4bf0b0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/mvp-definition/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mvp definition with structured process, quality checks, and system integration +--- + +# Mvp Definition + +## Purpose + +Create a comprehensive mvp definition that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mvp definition documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mvp definition +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mvp definition using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Mvp Definition + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/mvp-feature-list/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/mvp-feature-list/SKILL.md new file mode 100644 index 0000000..ef039ed --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/mvp-feature-list/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a mvp feature list with structured process, quality checks, and system integration +--- + +# Mvp Feature List + +## Purpose + +Create a comprehensive mvp feature list that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing mvp feature list documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the mvp feature list +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the mvp feature list using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Mvp Feature List + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/one-page-memo/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/one-page-memo/SKILL.md new file mode 100644 index 0000000..4134346 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/one-page-memo/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a one page memo with structured process, quality checks, and system integration +--- + +# One Page Memo + +## Purpose + +Create a comprehensive one page memo that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing one page memo documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the one page memo +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the one page memo using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# One Page Memo + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/partnership-strategy-startup/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/partnership-strategy-startup/SKILL.md new file mode 100644 index 0000000..2d02a51 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/partnership-strategy-startup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a partnership strategy startup with structured process, quality checks, and system integration +--- + +# Partnership Strategy Startup + +## Purpose + +Design and document a comprehensive partnership strategy startup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing partnership strategy startup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the partnership strategy startup +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the partnership strategy startup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Partnership Strategy Startup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/pitch-deck/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/pitch-deck/SKILL.md new file mode 100644 index 0000000..2e700a5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/pitch-deck/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a pitch deck with structured process, quality checks, and system integration +--- + +# Pitch Deck + +## Purpose + +Create a comprehensive pitch deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pitch deck documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pitch deck +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pitch deck using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Pitch Deck + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/pivot-assessment/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/pivot-assessment/SKILL.md new file mode 100644 index 0000000..9f9c262 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/pivot-assessment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a pivot assessment with structured process, quality checks, and system integration +--- + +# Pivot Assessment + +## Purpose + +Analyze and produce a comprehensive pivot assessment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pivot assessment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pivot assessment +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pivot assessment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Pivot Assessment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/pivot-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/pivot-plan/SKILL.md new file mode 100644 index 0000000..f12a8b6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/pivot-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a pivot plan with structured process, quality checks, and system integration +--- + +# Pivot Plan + +## Purpose + +Design and document a comprehensive pivot plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pivot plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pivot plan +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pivot plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Pivot Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/pmf-survey/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/pmf-survey/SKILL.md new file mode 100644 index 0000000..7dfead9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/pmf-survey/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a pmf survey with structured process, quality checks, and system integration +--- + +# Pmf Survey + +## Purpose + +Create a comprehensive pmf survey that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pmf survey documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pmf survey +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pmf survey using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Pmf Survey + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/pricing-experiment/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/pricing-experiment/SKILL.md new file mode 100644 index 0000000..f3b8abd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/pricing-experiment/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a pricing experiment with structured process, quality checks, and system integration +--- + +# Pricing Experiment + +## Purpose + +Create a comprehensive pricing experiment that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing pricing experiment documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the pricing experiment +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the pricing experiment using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Pricing Experiment + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/problem-validation/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/problem-validation/SKILL.md new file mode 100644 index 0000000..3ad1f4b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/problem-validation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a problem validation with structured process, quality checks, and system integration +--- + +# Problem Validation + +## Purpose + +Create a comprehensive problem validation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing problem validation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the problem validation +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the problem validation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Problem Validation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/product-market-fit/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/product-market-fit/SKILL.md new file mode 100644 index 0000000..9658e2d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/product-market-fit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a product market fit with structured process, quality checks, and system integration +--- + +# Product Market Fit + +## Purpose + +Create a comprehensive product market fit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing product market fit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the product market fit +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the product market fit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Product Market Fit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/remote-startup-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/remote-startup-playbook/SKILL.md new file mode 100644 index 0000000..ff6008a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/remote-startup-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a remote startup playbook with structured process, quality checks, and system integration +--- + +# Remote Startup Playbook + +## Purpose + +Design and document a comprehensive remote startup playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing remote startup playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the remote startup playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the remote startup playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Remote Startup Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/retention-analysis-startup/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/retention-analysis-startup/SKILL.md new file mode 100644 index 0000000..96fba38 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/retention-analysis-startup/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a retention analysis startup with structured process, quality checks, and system integration +--- + +# Retention Analysis Startup + +## Purpose + +Analyze and produce a comprehensive retention analysis startup that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing retention analysis startup documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the retention analysis startup +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the retention analysis startup using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Retention Analysis Startup + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/revenue-model-design/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/revenue-model-design/SKILL.md new file mode 100644 index 0000000..2ec7a51 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/revenue-model-design/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a revenue model design with structured process, quality checks, and system integration +--- + +# Revenue Model Design + +## Purpose + +Create a comprehensive revenue model design that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing revenue model design documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the revenue model design +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the revenue model design using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Revenue Model Design + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/side-project-validation/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/side-project-validation/SKILL.md new file mode 100644 index 0000000..975fd6a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/side-project-validation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a side project validation with structured process, quality checks, and system integration +--- + +# Side Project Validation + +## Purpose + +Create a comprehensive side project validation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing side project validation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the side project validation +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the side project validation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Side Project Validation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/solopreneur-playbook/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/solopreneur-playbook/SKILL.md new file mode 100644 index 0000000..058ce5f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/solopreneur-playbook/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a solopreneur playbook with structured process, quality checks, and system integration +--- + +# Solopreneur Playbook + +## Purpose + +Design and document a comprehensive solopreneur playbook that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing solopreneur playbook documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the solopreneur playbook +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the solopreneur playbook using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Solopreneur Playbook + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/startup-legal-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/startup-legal-checklist/SKILL.md new file mode 100644 index 0000000..5420d7b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/startup-legal-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a startup legal checklist with structured process, quality checks, and system integration +--- + +# Startup Legal Checklist + +## Purpose + +Analyze and produce a comprehensive startup legal checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing startup legal checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the startup legal checklist +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the startup legal checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Startup Legal Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/startup-metrics-dashboard/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/startup-metrics-dashboard/SKILL.md new file mode 100644 index 0000000..204f22c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/startup-metrics-dashboard/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a startup metrics dashboard with structured process, quality checks, and system integration +--- + +# Startup Metrics Dashboard + +## Purpose + +Analyze and produce a comprehensive startup metrics dashboard that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing startup metrics dashboard documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the startup metrics dashboard +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the startup metrics dashboard using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Startup Metrics Dashboard + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/team-building/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/team-building/SKILL.md new file mode 100644 index 0000000..186c8dd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/team-building/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a team building with structured process, quality checks, and system integration +--- + +# Team Building + +## Purpose + +Create a comprehensive team building that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing team building documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the team building +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the team building using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Team Building + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/term-sheet-negotiation/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/term-sheet-negotiation/SKILL.md new file mode 100644 index 0000000..9d6e329 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/term-sheet-negotiation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a term sheet negotiation with structured process, quality checks, and system integration +--- + +# Term Sheet Negotiation + +## Purpose + +Create a comprehensive term sheet negotiation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing term sheet negotiation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the term sheet negotiation +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the term sheet negotiation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Term Sheet Negotiation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/startup/trademark-search/SKILL.md b/clowdex-download/.claude/.claude/skills/startup/trademark-search/SKILL.md new file mode 100644 index 0000000..b22400e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/startup/trademark-search/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a trademark search with structured process, quality checks, and system integration +--- + +# Trademark Search + +## Purpose + +Create a comprehensive trademark search that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Startup & Entrepreneurship + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing trademark search documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the trademark search +- Identify gaps, opportunities, and risks +- Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+) +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the trademark search using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Talk to 100 potential customers before building + +## Output Format + +```markdown +# Trademark Search + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Lean Startup +- Business Model Canvas +- Lean Canvas +- Product-Market Fit Engine +- Venture Capital Method +- TAM/SAM/SOM + +## Key Metrics +- Monthly Burn Rate +- Runway (months) +- MoM Growth Rate +- CAC/LTV Ratio (target: 1:3+) +- Activation Rate +- Sean Ellis Test (40%+ very disappointed) + +## Best Practices +- Talk to 100 potential customers before building +- Default alive vs default dead — know your status +- Focus on one metric per stage +- 18 months runway minimum after raising +- Weekly team updates, monthly investor updates + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/accommodation-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/accommodation-comparison/SKILL.md new file mode 100644 index 0000000..5f2e95d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/accommodation-comparison/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a accommodation comparison with structured process, quality checks, and system integration +--- + +# Accommodation Comparison + +## Purpose + +Analyze and produce a comprehensive accommodation comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing accommodation comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the accommodation comparison +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the accommodation comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Accommodation Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/activity-planner/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/activity-planner/SKILL.md new file mode 100644 index 0000000..bc3ec10 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/activity-planner/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a activity planner with structured process, quality checks, and system integration +--- + +# Activity Planner + +## Purpose + +Design and document a comprehensive activity planner that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing activity planner documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the activity planner +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the activity planner using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Activity Planner + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/adventure-travel-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/adventure-travel-plan/SKILL.md new file mode 100644 index 0000000..7df738b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/adventure-travel-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a adventure travel plan with structured process, quality checks, and system integration +--- + +# Adventure Travel Plan + +## Purpose + +Design and document a comprehensive adventure travel plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing adventure travel plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the adventure travel plan +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the adventure travel plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Adventure Travel Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/airbnb-listing/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/airbnb-listing/SKILL.md new file mode 100644 index 0000000..a4dbdea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/airbnb-listing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a airbnb listing with structured process, quality checks, and system integration +--- + +# Airbnb Listing + +## Purpose + +Create a comprehensive airbnb listing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing airbnb listing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the airbnb listing +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the airbnb listing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Airbnb Listing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/bleisure-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/bleisure-guide/SKILL.md new file mode 100644 index 0000000..d96c458 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/bleisure-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a bleisure guide with structured process, quality checks, and system integration +--- + +# Bleisure Guide + +## Purpose + +Design and document a comprehensive bleisure guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing bleisure guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the bleisure guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the bleisure guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Bleisure Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/budget-travel-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/budget-travel-guide/SKILL.md new file mode 100644 index 0000000..491098b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/budget-travel-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a budget travel guide with structured process, quality checks, and system integration +--- + +# Budget Travel Guide + +## Purpose + +Design and document a comprehensive budget travel guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing budget travel guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the budget travel guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the budget travel guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Budget Travel Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/catering-menu/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/catering-menu/SKILL.md new file mode 100644 index 0000000..d624504 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/catering-menu/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a catering menu with structured process, quality checks, and system integration +--- + +# Catering Menu + +## Purpose + +Create a comprehensive catering menu that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing catering menu documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the catering menu +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the catering menu using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Catering Menu + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/conference-planning/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/conference-planning/SKILL.md new file mode 100644 index 0000000..8a84c85 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/conference-planning/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a conference planning with structured process, quality checks, and system integration +--- + +# Conference Planning + +## Purpose + +Design and document a comprehensive conference planning that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing conference planning documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the conference planning +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the conference planning using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Conference Planning + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/corporate-travel-policy/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/corporate-travel-policy/SKILL.md new file mode 100644 index 0000000..1e1d945 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/corporate-travel-policy/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a corporate travel policy with structured process, quality checks, and system integration +--- + +# Corporate Travel Policy + +## Purpose + +Create a comprehensive corporate travel policy that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing corporate travel policy documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the corporate travel policy +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the corporate travel policy using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Corporate Travel Policy + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/cost-comparison/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/cost-comparison/SKILL.md new file mode 100644 index 0000000..2d99da2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/cost-comparison/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a cost comparison with structured process, quality checks, and system integration +--- + +# Cost Comparison + +## Purpose + +Analyze and produce a comprehensive cost comparison that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing cost comparison documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the cost comparison +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the cost comparison using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Cost Comparison + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/crisis-management-hospitality/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/crisis-management-hospitality/SKILL.md new file mode 100644 index 0000000..9e15105 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/crisis-management-hospitality/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a crisis management hospitality with structured process, quality checks, and system integration +--- + +# Crisis Management Hospitality + +## Purpose + +Create a comprehensive crisis management hospitality that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing crisis management hospitality documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the crisis management hospitality +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the crisis management hospitality using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Crisis Management Hospitality + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/day-by-day-itinerary/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/day-by-day-itinerary/SKILL.md new file mode 100644 index 0000000..1dbb3da --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/day-by-day-itinerary/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a day by day itinerary with structured process, quality checks, and system integration +--- + +# Day By Day Itinerary + +## Purpose + +Create a comprehensive day by day itinerary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing day by day itinerary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the day by day itinerary +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the day by day itinerary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Day By Day Itinerary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/destination-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/destination-guide/SKILL.md new file mode 100644 index 0000000..cd5948a --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/destination-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a destination guide with structured process, quality checks, and system integration +--- + +# Destination Guide + +## Purpose + +Design and document a comprehensive destination guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing destination guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the destination guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the destination guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Destination Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/destination-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/destination-marketing/SKILL.md new file mode 100644 index 0000000..6eb4bb0 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/destination-marketing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a destination marketing with structured process, quality checks, and system integration +--- + +# Destination Marketing + +## Purpose + +Create a comprehensive destination marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing destination marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the destination marketing +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the destination marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Destination Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/dining-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/dining-guide/SKILL.md new file mode 100644 index 0000000..5fc17b2 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/dining-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a dining guide with structured process, quality checks, and system integration +--- + +# Dining Guide + +## Purpose + +Design and document a comprehensive dining guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dining guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dining guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dining guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Dining Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/dynamic-pricing-hospitality/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/dynamic-pricing-hospitality/SKILL.md new file mode 100644 index 0000000..839e76f --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/dynamic-pricing-hospitality/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a dynamic pricing hospitality with structured process, quality checks, and system integration +--- + +# Dynamic Pricing Hospitality + +## Purpose + +Create a comprehensive dynamic pricing hospitality that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing dynamic pricing hospitality documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the dynamic pricing hospitality +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the dynamic pricing hospitality using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Dynamic Pricing Hospitality + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/eco-tourism-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/eco-tourism-guide/SKILL.md new file mode 100644 index 0000000..4b18750 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/eco-tourism-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a eco tourism guide with structured process, quality checks, and system integration +--- + +# Eco Tourism Guide + +## Purpose + +Design and document a comprehensive eco tourism guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing eco tourism guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the eco tourism guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the eco tourism guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Eco Tourism Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/emergency-procedure/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/emergency-procedure/SKILL.md new file mode 100644 index 0000000..7edf770 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/emergency-procedure/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a emergency procedure with structured process, quality checks, and system integration +--- + +# Emergency Procedure + +## Purpose + +Create a comprehensive emergency procedure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing emergency procedure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the emergency procedure +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the emergency procedure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Emergency Procedure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/event-planning-venue/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/event-planning-venue/SKILL.md new file mode 100644 index 0000000..17d2488 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/event-planning-venue/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a event planning venue with structured process, quality checks, and system integration +--- + +# Event Planning Venue + +## Purpose + +Design and document a comprehensive event planning venue that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing event planning venue documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the event planning venue +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the event planning venue using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Event Planning Venue + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/excursion-brief/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/excursion-brief/SKILL.md new file mode 100644 index 0000000..8d0635d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/excursion-brief/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a excursion brief with structured process, quality checks, and system integration +--- + +# Excursion Brief + +## Purpose + +Create a comprehensive excursion brief that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing excursion brief documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the excursion brief +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the excursion brief using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Excursion Brief + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/family-vacation-planner/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/family-vacation-planner/SKILL.md new file mode 100644 index 0000000..1a9690c --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/family-vacation-planner/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a family vacation planner with structured process, quality checks, and system integration +--- + +# Family Vacation Planner + +## Purpose + +Design and document a comprehensive family vacation planner that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing family vacation planner documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the family vacation planner +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the family vacation planner using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Family Vacation Planner + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/food-tour-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/food-tour-plan/SKILL.md new file mode 100644 index 0000000..25b4f59 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/food-tour-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a food tour plan with structured process, quality checks, and system integration +--- + +# Food Tour Plan + +## Purpose + +Design and document a comprehensive food tour plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing food tour plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the food tour plan +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the food tour plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Food Tour Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/front-desk-procedure/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/front-desk-procedure/SKILL.md new file mode 100644 index 0000000..39978d3 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/front-desk-procedure/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a front desk procedure with structured process, quality checks, and system integration +--- + +# Front Desk Procedure + +## Purpose + +Create a comprehensive front desk procedure that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing front desk procedure documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the front desk procedure +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the front desk procedure using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Front Desk Procedure + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/group-travel-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/group-travel-plan/SKILL.md new file mode 100644 index 0000000..6eea629 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/group-travel-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a group travel plan with structured process, quality checks, and system integration +--- + +# Group Travel Plan + +## Purpose + +Design and document a comprehensive group travel plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing group travel plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the group travel plan +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the group travel plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Group Travel Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/guest-experience-audit/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/guest-experience-audit/SKILL.md new file mode 100644 index 0000000..229d2e4 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/guest-experience-audit/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a guest experience audit with structured process, quality checks, and system integration +--- + +# Guest Experience Audit + +## Purpose + +Analyze and produce a comprehensive guest experience audit that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing guest experience audit documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the guest experience audit +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the guest experience audit using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Guest Experience Audit + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/guest-feedback-analysis/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/guest-feedback-analysis/SKILL.md new file mode 100644 index 0000000..823ab1d --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/guest-feedback-analysis/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a guest feedback analysis with structured process, quality checks, and system integration +--- + +# Guest Feedback Analysis + +## Purpose + +Analyze and produce a comprehensive guest feedback analysis that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing guest feedback analysis documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the guest feedback analysis +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the guest feedback analysis using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Guest Feedback Analysis + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/guest-persona/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/guest-persona/SKILL.md new file mode 100644 index 0000000..41099bf --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/guest-persona/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a guest persona with structured process, quality checks, and system integration +--- + +# Guest Persona + +## Purpose + +Create a comprehensive guest persona that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing guest persona documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the guest persona +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the guest persona using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Guest Persona + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/health-safety-protocol/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/health-safety-protocol/SKILL.md new file mode 100644 index 0000000..d47b8b6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/health-safety-protocol/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a health safety protocol with structured process, quality checks, and system integration +--- + +# Health Safety Protocol + +## Purpose + +Create a comprehensive health safety protocol that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing health safety protocol documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the health safety protocol +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the health safety protocol using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Health Safety Protocol + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/honeymoon-planner/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/honeymoon-planner/SKILL.md new file mode 100644 index 0000000..6142394 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/honeymoon-planner/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a honeymoon planner with structured process, quality checks, and system integration +--- + +# Honeymoon Planner + +## Purpose + +Design and document a comprehensive honeymoon planner that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing honeymoon planner documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the honeymoon planner +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the honeymoon planner using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Honeymoon Planner + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/hotel-operations-sop/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/hotel-operations-sop/SKILL.md new file mode 100644 index 0000000..8a9c816 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/hotel-operations-sop/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a hotel operations sop with structured process, quality checks, and system integration +--- + +# Hotel Operations Sop + +## Purpose + +Create a comprehensive hotel operations sop that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hotel operations sop documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hotel operations sop +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hotel operations sop using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Hotel Operations Sop + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/hotel-review/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/hotel-review/SKILL.md new file mode 100644 index 0000000..f1d8c57 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/hotel-review/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a hotel review with structured process, quality checks, and system integration +--- + +# Hotel Review + +## Purpose + +Analyze and produce a comprehensive hotel review that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing hotel review documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the hotel review +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the hotel review using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Hotel Review + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/housekeeping-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/housekeeping-checklist/SKILL.md new file mode 100644 index 0000000..0a163b6 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/housekeeping-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a housekeeping checklist with structured process, quality checks, and system integration +--- + +# Housekeeping Checklist + +## Purpose + +Analyze and produce a comprehensive housekeeping checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing housekeeping checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the housekeeping checklist +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the housekeeping checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Housekeeping Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/itinerary-planner/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/itinerary-planner/SKILL.md new file mode 100644 index 0000000..3c16088 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/itinerary-planner/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a itinerary planner with structured process, quality checks, and system integration +--- + +# Itinerary Planner + +## Purpose + +Design and document a comprehensive itinerary planner that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing itinerary planner documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the itinerary planner +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the itinerary planner using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Itinerary Planner + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/loyalty-program-hospitality/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/loyalty-program-hospitality/SKILL.md new file mode 100644 index 0000000..734be7e --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/loyalty-program-hospitality/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a loyalty program hospitality with structured process, quality checks, and system integration +--- + +# Loyalty Program Hospitality + +## Purpose + +Design and document a comprehensive loyalty program hospitality that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing loyalty program hospitality documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the loyalty program hospitality +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the loyalty program hospitality using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Loyalty Program Hospitality + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/luxury-travel-concierge/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/luxury-travel-concierge/SKILL.md new file mode 100644 index 0000000..b3fe53b --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/luxury-travel-concierge/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a luxury travel concierge with structured process, quality checks, and system integration +--- + +# Luxury Travel Concierge + +## Purpose + +Create a comprehensive luxury travel concierge that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing luxury travel concierge documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the luxury travel concierge +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the luxury travel concierge using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Luxury Travel Concierge + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/multi-city-itinerary/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/multi-city-itinerary/SKILL.md new file mode 100644 index 0000000..63024d8 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/multi-city-itinerary/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a multi city itinerary with structured process, quality checks, and system integration +--- + +# Multi City Itinerary + +## Purpose + +Create a comprehensive multi city itinerary that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing multi city itinerary documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the multi city itinerary +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the multi city itinerary using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Multi City Itinerary + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/occupancy-optimization/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/occupancy-optimization/SKILL.md new file mode 100644 index 0000000..36a7da5 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/occupancy-optimization/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a occupancy optimization with structured process, quality checks, and system integration +--- + +# Occupancy Optimization + +## Purpose + +Create a comprehensive occupancy optimization that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing occupancy optimization documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the occupancy optimization +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the occupancy optimization using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Occupancy Optimization + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/packing-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/packing-checklist/SKILL.md new file mode 100644 index 0000000..0d219a7 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/packing-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a packing checklist with structured process, quality checks, and system integration +--- + +# Packing Checklist + +## Purpose + +Analyze and produce a comprehensive packing checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing packing checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the packing checklist +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the packing checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Packing Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/responsible-travel/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/responsible-travel/SKILL.md new file mode 100644 index 0000000..2d6d487 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/responsible-travel/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a responsible travel with structured process, quality checks, and system integration +--- + +# Responsible Travel + +## Purpose + +Create a comprehensive responsible travel that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing responsible travel documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the responsible travel +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the responsible travel using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Responsible Travel + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/restaurant-recommendation/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/restaurant-recommendation/SKILL.md new file mode 100644 index 0000000..e394e27 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/restaurant-recommendation/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a restaurant recommendation with structured process, quality checks, and system integration +--- + +# Restaurant Recommendation + +## Purpose + +Create a comprehensive restaurant recommendation that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing restaurant recommendation documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the restaurant recommendation +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the restaurant recommendation using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Restaurant Recommendation + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/revenue-management/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/revenue-management/SKILL.md new file mode 100644 index 0000000..68c0a64 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/revenue-management/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a revenue management with structured process, quality checks, and system integration +--- + +# Revenue Management + +## Purpose + +Create a comprehensive revenue management that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing revenue management documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the revenue management +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the revenue management using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Revenue Management + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/seasonal-promotion/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/seasonal-promotion/SKILL.md new file mode 100644 index 0000000..e57f6f9 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/seasonal-promotion/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a seasonal promotion with structured process, quality checks, and system integration +--- + +# Seasonal Promotion + +## Purpose + +Create a comprehensive seasonal promotion that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing seasonal promotion documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the seasonal promotion +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the seasonal promotion using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Seasonal Promotion + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/service-recovery/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/service-recovery/SKILL.md new file mode 100644 index 0000000..d78d6ff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/service-recovery/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a service recovery with structured process, quality checks, and system integration +--- + +# Service Recovery + +## Purpose + +Create a comprehensive service recovery that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing service recovery documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the service recovery +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the service recovery using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Service Recovery + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/solo-travel-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/solo-travel-guide/SKILL.md new file mode 100644 index 0000000..5dbfb82 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/solo-travel-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a solo travel guide with structured process, quality checks, and system integration +--- + +# Solo Travel Guide + +## Purpose + +Design and document a comprehensive solo travel guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing solo travel guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the solo travel guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the solo travel guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Solo Travel Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/sustainability-plan-travel/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/sustainability-plan-travel/SKILL.md new file mode 100644 index 0000000..b0832db --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/sustainability-plan-travel/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a sustainability plan travel with structured process, quality checks, and system integration +--- + +# Sustainability Plan Travel + +## Purpose + +Design and document a comprehensive sustainability plan travel that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing sustainability plan travel documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the sustainability plan travel +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the sustainability plan travel using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Sustainability Plan Travel + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/tour-guide-script/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/tour-guide-script/SKILL.md new file mode 100644 index 0000000..212a4cd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/tour-guide-script/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a tour guide script with structured process, quality checks, and system integration +--- + +# Tour Guide Script + +## Purpose + +Design and document a comprehensive tour guide script that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tour guide script documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tour guide script +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tour guide script using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Tour Guide Script + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/tourism-marketing/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/tourism-marketing/SKILL.md new file mode 100644 index 0000000..c2fb2ac --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/tourism-marketing/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a tourism marketing with structured process, quality checks, and system integration +--- + +# Tourism Marketing + +## Purpose + +Create a comprehensive tourism marketing that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing tourism marketing documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the tourism marketing +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the tourism marketing using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Tourism Marketing + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/travel-blog-post/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/travel-blog-post/SKILL.md new file mode 100644 index 0000000..96e4377 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/travel-blog-post/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a travel blog post with structured process, quality checks, and system integration +--- + +# Travel Blog Post + +## Purpose + +Create a comprehensive travel blog post that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing travel blog post documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the travel blog post +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the travel blog post using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Travel Blog Post + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/travel-budget-calculator/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/travel-budget-calculator/SKILL.md new file mode 100644 index 0000000..ad7d1ea --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/travel-budget-calculator/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a travel budget calculator with structured process, quality checks, and system integration +--- + +# Travel Budget Calculator + +## Purpose + +Create a comprehensive travel budget calculator that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing travel budget calculator documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the travel budget calculator +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the travel budget calculator using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Travel Budget Calculator + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/travel-document-checklist/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/travel-document-checklist/SKILL.md new file mode 100644 index 0000000..03eeed1 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/travel-document-checklist/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Analyze and produce a travel document checklist with structured process, quality checks, and system integration +--- + +# Travel Document Checklist + +## Purpose + +Analyze and produce a comprehensive travel document checklist that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing travel document checklist documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the travel document checklist +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the travel document checklist using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Travel Document Checklist + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/travel-photography-guide/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/travel-photography-guide/SKILL.md new file mode 100644 index 0000000..8b7fe08 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/travel-photography-guide/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a travel photography guide with structured process, quality checks, and system integration +--- + +# Travel Photography Guide + +## Purpose + +Design and document a comprehensive travel photography guide that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing travel photography guide documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the travel photography guide +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the travel photography guide using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Travel Photography Guide + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/travel-savings-plan/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/travel-savings-plan/SKILL.md new file mode 100644 index 0000000..26d7eff --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/travel-savings-plan/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a travel savings plan with structured process, quality checks, and system integration +--- + +# Travel Savings Plan + +## Purpose + +Design and document a comprehensive travel savings plan that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing travel savings plan documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the travel savings plan +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the travel savings plan using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Travel Savings Plan + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/upsell-strategy-hospitality/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/upsell-strategy-hospitality/SKILL.md new file mode 100644 index 0000000..9af6879 --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/upsell-strategy-hospitality/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Design and document a upsell strategy hospitality with structured process, quality checks, and system integration +--- + +# Upsell Strategy Hospitality + +## Purpose + +Design and document a comprehensive upsell strategy hospitality that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing upsell strategy hospitality documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the upsell strategy hospitality +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the upsell strategy hospitality using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Upsell Strategy Hospitality + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.claude/skills/travel/visa-requirements/SKILL.md b/clowdex-download/.claude/.claude/skills/travel/visa-requirements/SKILL.md new file mode 100644 index 0000000..3a270bd --- /dev/null +++ b/clowdex-download/.claude/.claude/skills/travel/visa-requirements/SKILL.md @@ -0,0 +1,132 @@ +--- +description: Create a visa requirements with structured process, quality checks, and system integration +--- + +# Visa Requirements + +## Purpose + +Create a comprehensive visa requirements that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time. + +**Category**: Travel & Hospitality + +## Inputs + +### Required +- **Objective**: What you want to achieve with this deliverable +- **Context**: Relevant background information + +### Optional +- **Constraints**: Any limitations or requirements to consider +- **Existing Work**: Previous documents or data to build on + +## System Context + +Before starting: +- Read `memory.md` for current project context and priorities +- Check `knowledge-base.md` for relevant learned rules or constraints +- Review any existing related documents in the project +- Note any active tasks in `Task Board.md` that relate to this deliverable + +## Process + +### Step 1: Context & Research +- Review any existing visa requirements documents in the project +- Check knowledge-base.md for relevant learned rules or constraints +- Check memory.md for current project context and priorities +- Identify key stakeholders and their requirements +- Select the most appropriate framework: Guest Journey Mapping, Revenue Management (RevPAR), Service Blueprint + +### Step 2: Analysis & Framework Application +- Apply the selected framework to structure the visa requirements +- Identify gaps, opportunities, and risks +- Define success metrics: RevPAR, Occupancy Rate, ADR (Average Daily Rate), Guest Satisfaction Score +- Document assumptions and dependencies +- Validate approach against industry best practices + +### Step 3: Build the Deliverable +- Structure the visa requirements using the output format below +- Include specific, actionable recommendations — not generic advice +- Add concrete numbers, timelines, and benchmarks where applicable +- Cross-reference with existing project documents for consistency +- Ensure every section adds value — remove filler + +### Step 4: Quality Validation +- [ ] All required inputs have been addressed +- [ ] Recommendations are specific and actionable (not vague) +- [ ] Numbers and benchmarks are realistic and sourced +- [ ] Output format matches the specification below +- [ ] No contradictions with knowledge-base rules +- [ ] Follows best practice: Respond to reviews within 24 hours + +## Output Format + +```markdown +# Visa Requirements + +## Executive Summary +[2-3 sentence overview of the deliverable and key recommendations] + +## Context & Objectives +- **Objective**: [What this achieves] +- **Audience**: [Who this is for] +- **Timeline**: [When this applies] + +## Analysis +[Structured analysis using the selected framework] + +## Recommendations +1. [Specific, actionable recommendation with expected impact] +2. [Specific, actionable recommendation with expected impact] +3. [Specific, actionable recommendation with expected impact] + +## Implementation +| Action | Owner | Timeline | Priority | +|--------|-------|----------|----------| +| [Action item] | [Who] | [When] | [High/Medium/Low] | + +## Success Metrics +| Metric | Current | Target | Measurement Method | +|--------|---------|--------|-------------------| +| [KPI] | [Baseline] | [Goal] | [How to measure] | + +## Risks & Mitigations +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| [Risk] | [H/M/L] | [H/M/L] | [Action] | + +## Next Steps +- [ ] [Immediate next action] +- [ ] [Follow-up action] +- [ ] [Review date] +``` + +## Applicable Frameworks +- Guest Journey Mapping +- Revenue Management (RevPAR) +- Service Blueprint +- Experience Economy Framework +- Sustainable Tourism Framework + +## Key Metrics +- RevPAR +- Occupancy Rate +- ADR (Average Daily Rate) +- Guest Satisfaction Score +- Online Review Score +- Repeat Guest Rate +- Booking Lead Time + +## Best Practices +- Respond to reviews within 24 hours +- Personalize guest experience with pre-stay surveys +- Dynamic pricing based on demand signals +- Train staff on service recovery (LEARN model) +- Sustainability credentials increasingly drive booking decisions + +## After Completion + +- Update `memory.md` if this deliverable changes project context or priorities +- Add any reusable learnings to `knowledge-nominations.md` +- If follow-up actions were identified, add them to `Task Board.md` +- Recommend related skills if additional work is needed diff --git a/clowdex-download/.claude/.mcp.json b/clowdex-download/.claude/.mcp.json new file mode 100644 index 0000000..260398e --- /dev/null +++ b/clowdex-download/.claude/.mcp.json @@ -0,0 +1,14 @@ +{ + "mcpServers": { + "context7": { + "command": "npx", + "args": ["-y", "@upstash/context7-mcp@latest"], + "description": "Live library documentation (Next.js, React, any npm package)" + }, + "memory": { + "command": "npx", + "args": ["-y", "@modelcontextprotocol/server-memory"], + "description": "Persistent knowledge graph for cross-session facts" + } + } +} diff --git a/clowdex-download/.claude/CLAUDE.local.md b/clowdex-download/.claude/CLAUDE.local.md new file mode 100644 index 0000000..37f1a76 --- /dev/null +++ b/clowdex-download/.claude/CLAUDE.local.md @@ -0,0 +1,18 @@ +# Personal Overrides + +This file is gitignored — your personal preferences that don't affect the team. + +## My Preferences + +- [Your preferred coding style differences] +- [Your editor/IDE specifics] +- [Your local environment quirks] + +## My API Keys & Services + +- [Note which services you have configured locally] +- [Never put actual keys here — use .env files] + +## My Workflow + +- [Any personal workflow adjustments] diff --git a/clowdex-download/.claude/CLAUDE.md b/clowdex-download/.claude/CLAUDE.md new file mode 100644 index 0000000..6195c18 --- /dev/null +++ b/clowdex-download/.claude/CLAUDE.md @@ -0,0 +1,279 @@ +# Claude Kontext — Clowdex + +Dieses Projekt nutzt Clowdex, ein umfassendes Workflow-System für Claude Code. +Lies immer zuerst `.claude/memory.md` bevor du handelst. + +## Schnellstart +- `/start` — Arbeit beginnen +- `/sync` — Zwischendurch Kontext auffrischen +- `/end-day` — Arbeitstag beenden +- `/audit` — Qualität der letzten Arbeit prüfen +- `/flush` — Kontext sicher leeren und frisch fortfahren +- `/unstick` — Wenn du feststeckst +- `/retro` — Sprint-Retrospektive +- `/system-audit` — Tiefenprüfung der Infrastruktur + +## Wichtige Dateien +- Memory: `.claude/memory.md` (aktueller Kontext — zuerst lesen) +- Wissensdatenbank: `.claude/knowledge-base.md` (systemweite Regeln — vor jeder Aufgabe lesen) +- Aufgabenboard: `Task Board.md` +- Notizblock: `Scratchpad.md` (schnelle Notizen, verarbeitet bei /sync, geleert bei /end-day) +- Tagesnotizen: `Daily Notes/` (automatisch erstellt durch /start) +- Wissensvorschläge: `.claude/knowledge-nominations.md` (Lernkandidaten — Sentinel prüft) +- Befehlsindex: `.claude/command-index.md` (alle Befehle mit Auslösern und Tools) + +## Systemarchitektur +- **Agenten** (`.claude/agents/`): Spezialisierte Sub-Agenten mit persistentem Memory + - `sentinel` — Qualitätskontrolle. Prüft Arbeit, befördert Wissen, schlägt SOP-Änderungen vor + - `pathfinder` — Hilft bei Blockaden. Ursachenanalyse und frische Lösungsansätze + - `decoder` — Übersetzt kryptische Fehlermeldungen in konkrete Fixes. Mustererkennung über Sessions hinweg + - `mirror` — Bringt dich dazu, das eigentliche Problem zu formulieren. Sokratisches Debugging + - `scribe` — Schreibt PR-Beschreibungen, Commit-Messages und Changelogs aus Diffs + - `compass` — Erkennt Scope-Creep. „Du wolltest X machen, aber jetzt machst du Y" + - `ledger` — Verfolgt technische Schulden. Katalogisiert Abkürzungen, empfiehlt Rückzahlung + - `scout` — Lernt neue Codebases schnell. Architektur-Maps, Identifikation wichtiger Dateien + - `historian` — Gräbt aus, warum Code existiert. Git Blame + Kontextrekonstruktion +- **Befehle** (`.claude/commands/`): Workflow-Rituale und Werkzeuge +- **Hooks** (`.claude/hooks/`): Deterministische Sicherheitsmaßnahmen (Logging, Validierung) +- **Logs** (`.claude/logs/`): Prüfprotokoll + Vorfallslog — automatisch durch Hooks befüllt +- **Skills** (`.claude/skills/`): Fachwissen, bei Bedarf geladen + +## Memory-Architektur (6 Stufen) +1. **memory.md** — Aktiver Session-Kontext (was du gerade machst) +2. **Agent Memory** (`.claude/agent-memory/`) — Persistentes Wissen pro Agent über Sessions hinweg +3. **Wissensdatenbank** (`.claude/knowledge-base.md`) — Systemweite Regeln (durch Sentinel geprüft) +4. **Wissensvorschläge** (`.claude/knowledge-nominations.md`) — Pipeline für Lernkandidaten +5. **MCP Knowledge Graph** — Strukturierte Entitäten und Relationen (falls Memory-MCP aktiviert) +6. **Tagesnotizen** — Chronologische Session-Historie und Übergabeprotokolle + +## Befehlsnutzung + +Alle Agenten können Systembefehle aufrufen. Lies `.claude/command-index.md` für den vollständigen Katalog. + +- **Selbst ausführen**: Wenn du die nötigen Tools hast, lies `.claude/commands/{name}.md` und folge der Anleitung direkt. +- **Empfehlen**: Wenn dir Tools fehlen, gib `RECOMMEND: /command [args] — [reason]` an den Orchestrator aus. +- Agenten sollten Befehle proaktiv aufrufen, wenn die Auslösebedingungen zutreffen. + +## Schnellzugriff — Wo du was findest + +| Du brauchst... | Prüfe zuerst | Dann | +|---|---|---| +| Was mache ich gerade? | `memory.md` → Now | Task Board → Today | +| Wie geht ein Verfahren? | `.claude/commands/` oder `.claude/skills/` | CLAUDE.md | +| Eine Regel oder Erkenntnis | `knowledge-base.md` | Agent Memory | +| Was an einem bestimmten Tag passiert ist | `Daily Notes/MMDDYY.md` | Prüfprotokoll | +| Was früher schiefgelaufen ist | `knowledge-base.md` → Hard Rules | Agent Memory → Known Patterns | +| Welche Befehle es gibt | `.claude/command-index.md` | `.claude/commands/{name}.md` | + +## Session-Zustand + +Sessions haben begrenzten Kontext. Aufwendige Operationen verbrauchen ihn schnell. + +**Automatisches Sicherheitsnetz (Hooks):** +- `PreCompact`-Hook sichert den Zustand vor der Auto-Komprimierung +- `SessionStart(compact)`-Hook stellt den Kontext nach der Komprimierung wieder her +- `SessionStart(user)`-Hook setzt veraltete Gate-Dateien bei jeder neuen Session zurück + +**Validierungschecks (PreToolUse Write|Edit — harte Blockaden):** +- **knowledge-base.md**: Jeder Eintrag braucht `[Source:]`-Herkunft, max 200 Zeilen, kein TBD/TODO +- **memory.md**: Max 100 Zeilen (nur Write) +- **settings.json**: Muss valides JSON sein (defektes JSON bricht alle Hooks) +- **Agent-Definitionen** (`.claude/agents/*.md`): Kein TBD/TODO — Anweisungen müssen definitiv sein +- **Ohne Gate** (iterativ): Daily Notes, Scratchpad, Templates, Logs, Commands, Skills + +**Selbstüberwachung (weiche Signale — Claudes Verantwortung):** +- Nach ~30+ Tool-Aufrufen oder 3+ großen Datei-Lesevorgängen: `/flush` proaktiv ausführen +- Bei „compacting conversation"-Warnung: `/flush` sofort ausführen +- Bei Qualitätsverlust (Wiederholungen, übersehene Details): `/flush` ausführen +- Nach Abschluss einer mehrstufigen Aufgabe: `/flush` vor der nächsten unzusammenhängenden Aufgabe erwägen +- Beim Wechsel zwischen Aufgabenbereichen: Grenze anerkennen, `/flush` bei großen Wechseln bevorzugen + +**So funktioniert /flush:** Destilliert den Session-Zustand in memory.md + Tagesnotiz-Übergabe und bewahrt Suchpfade. Setzt dann automatisch fort, indem der komprimierte Kontext neu geladen und die nächste Aktion ausgeführt wird. Nahtlos für den Nutzer. + +## Wartung +- memory.md kompakt halten (<100 Zeilen) +- Veraltete Einträge konsequent entfernen +- Done-Liste freitags leeren +- Vorfallslog bei /sync und /end-day prüfen +- Sentinel schlägt SOP-Änderungen vor — Nutzer genehmigt vor Übernahme + +--- + +## PROJEKTABLAUF-PROTOKOLL (Verbindlich) + +Du folgst bei JEDEM Projekt diesem 7-Phasen-Protokoll. +Du darfst KEINE Phase überspringen. +Du prüfst vor jedem Phasenwechsel die Exit-Kriterien der aktuellen Phase. +Wenn Exit-Kriterien nicht erfüllt sind, bleibst du in der Phase und kommunizierst was fehlt. + +### Aktueller Projektstatus (wird von dir gepflegt) +``` +PHASE: [ ] 1-Scope [ ] 2-Architektur [ ] 3-Entwicklung + [ ] 4-QA [ ] 5-Security [ ] 6-Deployment [ ] 7-Doku +AKTUELLE PHASE: ___ +LETZTER SCHRITT: ___ +OFFEN: ___ +``` + +--- + +### PHASE 1 — Scope & Setup +**Trigger:** Neues Projekt wird gestartet oder `/project-start` wird aufgerufen. + +**Du führst aus (in dieser Reihenfolge):** +1. Frage den Nutzer: Projektname, Projekttyp (SaaS-App / n8n-Workflow / Python-Script / Static-Website), DSGVO-relevant (ja/nein) +2. Kopiere das Base Project: `cp -r ~/C-Stone\ Cloud/Claude\ Code/projekte/Base\ Project ~/C-Stone\ Cloud/Claude\ Code/projekte/[PROJEKTNAME]` +3. Führe `rag_query` aus mit: "Gibt es ähnliche Projekte oder Vorlagen für [PROJEKTNAME]?" +4. Lege GitHub-Repo an: `gh repo create c-stone-[projektname] --private --source=. --push` +5. Befülle `Task Board.md` mit mindestens 5 konkreten Tickets aus dem Scope +6. Aktualisiere `memory.md`: Projektname, Typ, DSGVO-Status, Startdatum +7. Trage in Projektstatus oben ein: PHASE = 1-Scope ✅, wechsle zu Phase 2 + +**Exit-Kriterien (alle müssen erfüllt sein):** +- [ ] Projektordner unter `projekte/[NAME]/` vorhanden +- [ ] GitHub-Repo angelegt, initialer Push erfolgt +- [ ] DSGVO-Anforderung in memory.md dokumentiert +- [ ] Task Board hat ≥ 5 Tickets +- [ ] RAG-Query ausgeführt, Ergebnis in Scratchpad.md notiert + +--- + +### PHASE 2 — Architektur +**Trigger:** Phase 1 Exit-Kriterien erfüllt. + +**Stack-Entscheidung (automatisch nach Projekttyp):** +- SaaS-App → FastAPI + PostgreSQL + Redis + React/Vite + Docker Compose + Traefik +- n8n-Workflow → n8n Webhook + Flask Microservice + SeaTable +- Python-Script → Python 3 + boto3 (Bedrock Frankfurt) + openpyxl wenn Excel +- Static-Website → HTML5 + CSS3 + Vanilla JS, kein Backend + +**Du führst aus:** +1. Erstelle Ordnerstruktur passend zum Stack +2. Erstelle `docker-compose.yml` mit Traefik-Labels für `[projekt].c-stone-dev.com` +3. Erstelle `.env.example` (alle Keys als Platzhalter, NIE echte Werte) +4. Erstelle `.gitignore` (muss enthalten: `.env`, `.env.*`, `*.pem`, `node_modules/`, `__pycache__/`, `.DS_Store`) +5. Erstelle `.nextcloudignore` (muss enthalten: `node_modules/`, `__pycache__/`, `.env`, `*.db`, `venv/`) +6. Entwirf Datenbankschema in `docs/schema.md` (bei SaaS-Apps) +7. Notiere Architekturentscheidungen in `knowledge-base.md` des Projekts +8. Initialer Commit: `git add -A && git commit -m "chore: Projektstruktur und Architektur"` + +**Exit-Kriterien:** +- [ ] Ordnerstruktur angelegt +- [ ] docker-compose.yml vorhanden mit Traefik-Labels +- [ ] .gitignore und .nextcloudignore vorhanden und vollständig +- [ ] .env.example vorhanden (keine echten Werte) +- [ ] Architektur in knowledge-base.md dokumentiert +- [ ] Commit "chore: Projektstruktur" auf GitHub + +--- + +### PHASE 3 — Entwicklung (Iterativ) + +**Tool-Wahl (du empfiehlst dem Nutzer aktiv das richtige Tool):** + +| Aufgabe | Tool | Modell | +|---|---|---| +| Tab-Autocomplete, einzelne Zeilen | Continue.dev | qwen2.5-coder:14b | +| Einzelne Funktion, Snippet (≤ 2 Dateien) | Continue.dev | devstral:24b / qwen3:30b | +| Ordnerstruktur, Boilerplate (≥ 3 Dateien) | Cline | devstral:24b (lokal) | +| Feature über mehrere Dateien | Cline | Qwen3 235B (Bedrock) | +| Tests schreiben + ausführen + fixen | Cline | Devstral 123B (Bedrock) | +| Refactoring über gesamte Codebase | Cline | Qwen3 235B (Bedrock) | +| SSH Hetzner, Docker, Playwright, RAG-Query | Claude Code | Claude Sonnet 4.6 | + +**Du führst aus (pro Feature-Zyklus):** +1. Feature-Branch anlegen: `git checkout -b feature/[beschreibung]` +2. Empfehle dem Nutzer das passende Tool für diese Aufgabe +3. Nach Implementierung: Lokal testen +4. Atomic Commit mit Conventional-Commit-Message (`feat:` / `fix:` / `refactor:` / `test:` / `security:` / `docs:` / `chore:`) +5. Nach 3–4h: `/sync` aufrufen +6. Bei Blockade: `/unstick` aufrufen + +**Sicherheitsregel:** NIEMALS echte Credentials in Dateien · NIEMALS .env committen · IMMER .gitignore prüfen + +**Exit-Kriterien:** +- [ ] Alle Features aus Task Board implementiert +- [ ] Code läuft lokal in Docker ohne Fehler +- [ ] Keine ERROR-Logs in `docker logs` +- [ ] Alle Commits auf GitHub gepusht + +--- + +### PHASE 4 — QA & Testing + +1. `pytest tests/ -v` — 0 Fehler +2. `docker compose build --no-cache && docker compose up -d` +3. Playwright E2E: Happy Path, Screenshots 1440px + 375px +4. Swagger unter `http://localhost:8000/docs` erreichbar? +5. DSGVO: Logs anonym? AWS Region = `eu-central-1`? +6. `/audit` + +**Exit-Kriterien:** pytest grün · Docker "Up" · Playwright grün · /audit OK · DSGVO geprüft + +--- + +### PHASE 5 — Security Gate (PFLICHT, nicht überspringbar) + +1. Secrets-Scan: `git grep -rn "AWS_ACCESS\|AWS_SECRET\|PASSWORD\|SECRET_KEY\|TOKEN\|api_key" --include="*.py" --include="*.js" --include="*.ts" -- ':!.env.example'` +2. Staged-Files: `git diff --cached --name-only | grep -i "\.env\|credentials\|secret\|key"` +3. .env in .nextcloudignore? +4. Auth: alle Endpunkte außer `/health` + `/docs` hinter `Depends(get_current_user)`? +5. slowapi auf kritischen Endpunkten? +6. `pip-audit` + `npm audit` +7. `grep -r "eu-central-1\|eu-north-1" backend/ --include="*.py"` + +**Bei EINEM Fehler: KEIN Deployment.** + +**Exit-Kriterien:** Secrets 0 · .env ausgeschlossen · Auth OK · keine kritischen CVEs · DSGVO-Region bestätigt + +--- + +### PHASE 6 — Deployment auf Hetzner + +1. Finaler Push + Tag +2. `ssh root@n8n.c-stone-dev.com` +3. Repo klonen/pullen, .env manuell anlegen +4. `docker compose build --no-cache && docker compose up -d` +5. `docker exec [PROJEKTNAME]-backend-1 alembic upgrade head` +6. 5 Minuten Logs beobachten +7. Playwright E2E gegen `https://[projekt].c-stone-dev.com` + +**Exit-Kriterien:** alle services "Up" · HTTPS erreichbar · E2E grün · 5min Logs OK · Git-Tag gesetzt + +--- + +### PHASE 7 — Dokumentation & Wissenstransfer + +1. README.md aktualisieren +2. `cp README.md ~/cstone-rag/inbox/[PROJEKTNAME]-readme.md` +3. knowledge-base.md ≥ 3 Einträge +4. `/retro` + `/end-day` +5. Neues Projekt in C-Stone-Setup-Public.html eintragen + +**Exit-Kriterien:** README vollständig · RAG befüllt · knowledge-base ≥ 3 · /retro ausgeführt + +--- + +## VERHALTEN BEI PHASENÜBERGÄNGEN + +Abschluss: `✅ PHASE [N] ABGESCHLOSSEN — Wechsle zu PHASE [N+1]: [Name] — Erste Aktion: [...]` + +Nicht abgeschlossen: `⏸ PHASE [N] NOCH NICHT ABGESCHLOSSEN — Fehlend: [...] — Ich behebe jetzt: [...]` + +Überspringen-Anfrage: `⚠️ Fehlende Checks: [...] — Bist du sicher? Antworte mit "ja, überspringen"` + +--- + +## DSGVO-REGEL: GITHUB & EXTERNE DIENSTE (Nicht verhandelbar) + +GitHub (MCP + CLI + gh) NUR für technische Inhalte — NIEMALS für: +- Kundennamen, E-Mail-Adressen, Telefonnummern realer Personen +- Inhalte aus Kundengesprächen oder Beratungssessions +- Daten aus SeaTable (CRM, Leads, Kontakte) + +**Begründung:** GitHub läuft auf US-Servern (Microsoft) — DSGVO Art. 44 ff. + +**Prüfpflicht:** Vor jedem GitHub-Befehl auf Personenbezug prüfen. Bei Unsicherheit: +`⛔ DSGVO-CHECK: "[Text]" — Formulierung anpassen oder nur lokal speichern.` + +**Bedrock-Region:** Nur eu-central-1 (Frankfurt) oder eu-north-1 (Stockholm). Niemals US-Regionen. diff --git a/clowdex-download/.claude/SETUP.md b/clowdex-download/.claude/SETUP.md new file mode 100644 index 0000000..5c70a32 --- /dev/null +++ b/clowdex-download/.claude/SETUP.md @@ -0,0 +1,149 @@ +# Clowdex — Schnellstart + +In 3 Schritten zum vollständigen Claude Code Workflow-System. + +--- + +## 1. Claude Code installieren + +Falls Claude Code bereits installiert ist (`claude --version`), überspringe diesen Schritt. + +```bash +# Mac / Linux / WSL +curl -fsSL https://claude.ai/install.sh | bash + +# Windows PowerShell +irm https://claude.ai/install.ps1 | iex +``` + +Voraussetzung: Ein kostenpflichtiger Anthropic-Plan (Pro $20/Monat, Max $100–200/Monat, oder Teams/Enterprise). + +> **Hinweis:** Wenn die Umgebungsvariable `ANTHROPIC_API_KEY` gesetzt ist, wird über dein API-Konto abgerechnet statt über dein Abo. Mit `unset ANTHROPIC_API_KEY` lässt sich das zurücksetzen. + +> **Voraussetzung:** Die Sicherheits-Hooks benötigen `jq` (ein JSON-Prozessor für die Kommandozeile). Installiere es, falls noch nicht vorhanden: +> ```bash +> # Mac +> brew install jq +> +> # Ubuntu / Debian +> sudo apt-get install jq +> +> # Windows (via Chocolatey) +> choco install jq +> ``` +> Prüfe mit `jq --version`. Ohne `jq` laufen die Hooks zwar, aber Sicherheitsprüfungen (Backup-Validierung, Vollständigkeitschecks, Blockierung gefährlicher Befehle) werden stillschweigend übersprungen. + +## 2. Dateien ins Projekt kopieren + +Entpacke alles und kopiere es in dein Projekt-Verzeichnis: + +```bash +cd /path/to/your/project +cp -r /path/to/clowdex-download/* . +cp -r /path/to/clowdex-download/.claude . +``` + +Dadurch werden das `.claude/`-Systemverzeichnis, `CLAUDE.md`, `Task Board.md`, `Scratchpad.md` und `Daily Notes/` angelegt. + +Falls du bereits ein `.claude/`-Verzeichnis hast, führe die Dateien manuell zusammen — überschreibe nicht deine bestehenden Einstellungen oder deinen Memory. + +## 3. Claude Code starten und Onboarding durchführen + +```bash +claude +``` + +Füge anschließend den folgenden Onboarding-Prompt ein. Claude scannt damit dein Projekt, übernimmt das Clowdex-System und richtet alles für dein Setup ein. + +--- + +## Onboarding-Prompt (kopiere diesen Text in Claude Code) + +``` +Ich habe gerade Clowdex in dieses Projekt installiert. Die Systemdateien liegen in .claude/ und die Hauptanweisungen in CLAUDE.md. + +Bitte führe folgendes aus: + +1. Lies CLAUDE.md um die gesamte Systemarchitektur zu verstehen. +2. Lies .claude/memory.md und .claude/knowledge-base.md. +3. Lies .claude/command-index.md um alle verfügbaren Befehle kennenzulernen. +4. Scanne meine Projektstruktur (Dateien, Ordner, Sprache, Framework, Abhängigkeiten). +5. Zeige mir eine Zusammenfassung dessen, was du gefunden hast. +6. Stelle mir dann ein paar gezielte Fragen, um das System auf meine Bedürfnisse anzupassen: + - Was sind meine Hauptziele mit diesem Projekt? + - Wie sieht mein typischer Workflow aus? + - Welche Aufgaben kosten mich die meiste Zeit (oder möchte ich automatisieren)? + - Gibt es Tools, Plattformen oder Dienste, die ich regelmäßig nutze? +7. Aktualisiere auf Basis meiner Antworten und deines Scans die memory.md mit: + - Projektname und Beschreibung + - Sprache/Framework/Build-Tool + - Wichtige Dateipfade + - Erkannte Muster + - Meine Ziele und Workflow-Präferenzen +8. Prüfe die Skills in .claude/skills/ — empfiehl die Kategorien und konkreten Skills, die für mein Projekt und meine Ziele am relevantesten sind. +9. Führe /start aus, um den täglichen Workflow zu initialisieren. + +Scanne zuerst, stelle dann Fragen — warte nicht auf mich, bevor du den ersten Scan durchführst. +``` + +--- + +## Was du gerade installiert hast + +**Mehrstufiger Memory** — Claude merkt sich Kontext über Sessions hinweg, lernt aus Fehlern und wird mit der Zeit besser. + +**9 spezialisierte Agenten** — Sentinel (Qualitätssicherung), Pathfinder, Decoder, Mirror, Scribe, Compass, Ledger, Scout, Historian. Sie werden automatisch über Befehle ausgelöst. + +**21 Befehle** — `/start`, `/sync`, `/end-day`, `/flush`, `/audit`, `/onboard`, `/review`, `/retro`, `/launch`, `/report` und weitere. Einfach in Claude Code eintippen — der Rest läuft automatisch. + +**1.792 Skills in 32 Kategorien** — Cybersecurity, Agriculture, AI Automation, Construction, Consulting, Content, Customer Success, Data, Design, Development, Ecommerce, Education, Email, Energy, Finance, Fitness & Wellness, Food & Beverage, Healthcare, HR, Legal, Marketing, Media, Nonprofit, Operations, Product, Productivity, Real Estate, Sales, SEO, Social Media, Startup, Travel. + +**9 automatische Prüfungen** — Deterministische Sicherheitsnetze bei jedem Durchlauf: blockiert gefährliche Shell-Befehle, sichert Dateien vor dem Überschreiben, erkennt unvollständige Inhalte und protokolliert alles. + +**Lernfähiges System** — Claude erkennt Muster, schlägt Erkenntnisse vor und der Sentinel befördert bestätigte Regeln ins Wissensarchiv. Das System wird schlauer, je mehr du es nutzt. + +## Täglicher Workflow + +| Wann | Was | +|------|-----| +| Morgens | `/start` → arbeiten → `/sync` (bei Aufgabenwechsel) | +| Nachmittags | arbeiten → `/flush` (bei hoher Kontextlast) → arbeiten | +| Abends | `/end-day` | + +## Befehle + +| Befehl | Einsatzzweck | +|--------|-------------| +| `/start` | Beginn einer Arbeitssitzung | +| `/sync` | Zwischendurch Kontext auffrischen | +| `/flush` | Zwischen unzusammenhängenden Aufgaben oder bei Qualitätsverlust | +| `/end-day` | Ende einer Arbeitssitzung | +| `/audit` | Nach Abschluss wichtiger Arbeiten | +| `/onboard` | Neues Projekt kennenlernen | +| `/unstick` | Wenn du feststeckst | +| `/review` | Code- oder Arbeits-Review | +| `/retro` | Sprint-Retrospektive | +| `/system-audit` | Tiefenprüfung der Systeminfrastruktur | + +## FAQ + +**Muss ich programmieren können?** +Nein. Alles funktioniert in natürlicher Sprache. + +**Funktioniert das mit jedem Projekt?** +Ja — egal welche Sprache, welches Framework oder welche Struktur. Das Onboarding passt sich automatisch an. + +**Wie bekomme ich Updates?** +Updates werden per E-Mail an die Adresse gesendet, mit der du gekauft hast. + +## Tipps + +1. **Nutze `/flush` zwischen verschiedenen Aufgaben.** Kontextverschmutzung ist der häufigste Grund für Qualitätsverlust. +2. **Halte memory.md unter 100 Zeilen.** Lösche regelmäßig Veraltetes. +3. **Lass die Wissensdatenbank natürlich wachsen.** Befülle sie nicht vorab — lass den Sentinel echte Erkenntnisse befördern. +4. **Vertraue den Hooks.** Sie fangen ab, was Anweisungen übersehen. +5. **Probiere `/unstick` wenn du blockiert bist.** Besser als im Kreis zu drehen. + +--- + +**Hilfe nötig?** hello@rech.studio diff --git a/clowdex-download/.claude/Scratchpad.md b/clowdex-download/.claude/Scratchpad.md new file mode 100644 index 0000000..dc0b223 --- /dev/null +++ b/clowdex-download/.claude/Scratchpad.md @@ -0,0 +1,5 @@ +# Scratchpad + +Quick capture. Processed during /sync, cleared at /end-day. + +--- diff --git a/clowdex-download/.claude/Task Board.md b/clowdex-download/.claude/Task Board.md new file mode 100644 index 0000000..aa3a819 --- /dev/null +++ b/clowdex-download/.claude/Task Board.md @@ -0,0 +1,13 @@ +# Task Board + +## Today +- [ ] Set up project with Clowdex (`/start`) + +## This Week +- + +## Backlog +- + +## Done +- diff --git a/docker-compose.yml b/docker-compose.yml new file mode 100644 index 0000000..7a0cd57 --- /dev/null +++ b/docker-compose.yml @@ -0,0 +1,47 @@ +version: '3.8' + +services: + backend: + build: + context: . + dockerfile: Dockerfile.backend + container_name: invoice-check-backend + ports: + - "8001:8001" + environment: + - DATABASE_URL=postgresql://postgres:postgres@db:5432/invoice_check + - SECRET_KEY=${SECRET_KEY} + - AWS_DEFAULT_REGION=eu-central-1 + depends_on: + - db + networks: + - traefik_web + - invoice-check-network + labels: + - "traefik.enable=true" + - "traefik.http.routers.invoice-check.entrypoints=websecure" + - "traefik.http.routers.invoice-check.rule=Host(`invoice-check.c-stone-dev.com`)" + - "traefik.http.routers.invoice-check.tls=true" + - "traefik.http.services.invoice-check.loadbalancer.server.port=8001" + + db: + image: postgres:16-alpine + container_name: invoice-check-db + environment: + - POSTGRES_USER=postgres + - POSTGRES_PASSWORD=postgres + - POSTGRES_DB=invoice_check + volumes: + - postgres-data:/var/lib/postgresql/data + networks: + - invoice-check-network + # Kein ports-Mapping - DB nur Docker-intern + +networks: + traefik_web: + external: true + invoice-check-network: + driver: bridge + +volumes: + postgres-data: diff --git a/docs/schema.md b/docs/schema.md new file mode 100644 index 0000000..b0dafab --- /dev/null +++ b/docs/schema.md @@ -0,0 +1,101 @@ +# Datenbankschema — C-Stone Invoice Check + +## Overview + +``` +┌─────────────┐ ┌─────────────┐ ┌─────────────────┐ +│ Users │ │ EmailLogs │ │ Invoices │ +├─────────────┤ ├─────────────┤ ├─────────────────┤ +│ id (PK) │───── │ email_id │───── │ id (PK) │ +│ username │ │ subject │ │ email_id │ +│ password │ │ from │ │ subject │ +│ active │ │ date │ │ from │ +└─────────────┘ │ folder │ │ date │ + │ keywords │ │ amount │ + │ attachment │ │ tax_amount │ + │ processed │ │ tax_type │ + └─────────────┘ │ issuer │ + │ file_path │ + └─────────────────┘ + │ + │ + ┌─────────────────┐ + │ InvoiceDetails │ + ├─────────────────┤ + │ id (PK) │ + │ invoice_id (FK) │ + │ raw_text │ + │ parsed_data │ + │ confidence │ + └─────────────────┘ +``` + +## Tabellen + +### users +Speichert Benutzer für die Web-Interface Authentifizierung. + +| Spalte | Typ | Beschreibung | +|--------|-----|--------------| +| id | Integer | Primärschlüssel | +| username | String | Benutzername (unique) | +| hashed_password | String | Passwort-Hash (bcrypt) | +| is_active | Boolean | Account aktiviert | +| created_at | DateTime | Erstellungsdatum | + +### email_logs +Protokolliert jede geprüfte Email. + +| Spalte | Typ | Beschreibung | +|--------|-----|--------------| +| id | Integer | Primärschlüssel | +| email_id | String | IMAP UID (unique) | +| subject | String | Betreff | +| from | String | Absender | +| date | DateTime | Empfangsdatum | +| folder | String | Mail-Ordner | +| matched_keywords | JSON | Gefundene Keywords | +| has_attachment | Boolean | Hat Anhang | +| attachment_type | String | pdf/doc/docx | +| processed | Boolean | Verarbeitet | +| invoice_id | Integer | Verweis auf Invoice (nullable) | +| created_at | DateTime | Erstellungsdatum | + +### invoices +Speichert die Rechnungs-Metadaten. + +| Spalte | Typ | Beschreibung | +|--------|-----|--------------| +| id | Integer | Primärschlüssel | +| email_id | String | IMAP UID der Original-Email | +| subject | String | Email-Betreff | +| from | String | Email-Absender | +| date | DateTime | Email-Datum | +| invoice_number | String | Rechnungsnummer | +| invoice_date | DateTime | Rechnungsdatum | +| amount | Float | Rechnungssumme | +| tax_amount | Float | Steuerbetrag | +| tax_rate | Float | Steuersatz (0.0, 0.19, etc.) | +| tax_type | String | "MwSt", "Umsatzsteuer", "VAT", "ohne" | +| issuer_name | String | Rechnungsausteller | +| file_path | String | Vollständiger Pfad auf Evo-X2 | +| storage_year | Integer | Jahr (2025, 2026) | +| storage_path | String | Unterordner (z.B. "2025/ohne MwSt") | +| processed | Boolean | Verarbeitung abgeschlossen | +| processing_error | Text | Fehlermeldung (nullable) | +| confidence_score | Float | 0.0 - 1.0 | +| created_at | DateTime | Erstellungsdatum | +| updated_at | DateTime | Letzte Änderung | + +### invoice_details +Speichert erweiterte Daten (roher PDF-Text, geparste Daten). + +| Spalte | Typ | Beschreibung | +|--------|-----|--------------| +| id | Integer | Primärschlüssel | +| invoice_id | Integer | Verweis auf Invoice | +| raw_text | Text | Extrahierter PDF-Text | +| parsed_data | JSON | Strukturierte Daten | +| confidence_breakdown | JSON | Einzelne Confidence-Werte | +| processing_notes | Text | Anmerkungen | +| created_at | DateTime | Erstellungsdatum | diff --git a/frontend/package.json b/frontend/package.json new file mode 100644 index 0000000..e69de29 diff --git a/frontend/vite.config.ts b/frontend/vite.config.ts new file mode 100644 index 0000000..e69de29